tetanus | : shell : A proof-of-concept reverse-shell written in rust | Security Testing library

It sounds like you want to do:

The table you are calling a Pivot table, in standard relational design is typically referred to as a Many-to-many resolver table. This is because, at a high level your design involves a relationship between patient and Vaccines that is Many to many.

• A Patient can take many vaccines
• A vaccine can be taken by many Patients

Now to your specific question:

There is no perfect answer here, because this is a business rule that exists outside of the normal relations, but I would do one of 2 different things.

The first thing about Vaccines, is that AFAIK, multiple vaccines are often combined in one shot. So this cries out for either a "shot" table, or the ability of the vaccine table to support a parent child hierarchy.

"Took all vaccines" seems to me to be a non-specific and factually inaccurate representation, but then again I don't know your application.

Given that, the simplest and best answer in my opinion, is to add a row in Vaccine named "All Vaccines (Patient under 18 years of age)".

Then you no longer need to concern yourself with NULL foreign keys, which you certainly don't want in a many-to-many resolution table.

The other alternative, would be to implement the shot container table (shot 1 -> Many vaccines) and have patient_shot replace patient_vaccine. You could also do something similar by combining shot and vaccine into a single hierarchical table, where vaccines can have a parent "vaccine" row.

Not sure if it is what you are trying to achieve, I hope this could be helpful

Your inputs don't set a value attribute and as MDN puts it:

If you omit the value attribute in the HTML, the submitted form data assigns the value "on" to the group.

Either set a value attribute :

You could use this:

You could use this:

use an If … ElseIf … Else … End If statement and increase j.

This example illustrates how you can use factor(x, levels) to make sure bars in the same group are placed together. In the ggplot call, you can map the grouping variable to the fill aesthetic to visually seperate the groups. Use stat = "unique" to take unique value instead of making a count (where the height of each bar is determined by the number of corresponding rows in df).

You can use: