As per mustaccio's comment, when you have the same
PrimaryKey defined in each of your
Tables, that then guarantees a one-to-one relationship is enforced between each
Table. In other words, based on the schema of your
Tables provided in your question, you won't ever be able to have more than one Animal at one Event, or more than one Restriction for a specific Animal, etc. They all share the same
unique Location ID.
If that meets your needs then your design is ok.
But if you want to be able to have multiple Animals at multiple Events with varying Restrictions for different locations etc, then you might be better off with the following design:
Add a fourth
Table called Locations with the Location ID
Remove the Location ID
unique constraint) from all the other
tables and instead create a
ForeignKey relationship between it and your Locations
table on Location ID.
Add a new
unique PrimaryKey field to the Events, Animals, Restrictions
tables with the appropriate names (e.g. Event ID for the Events
table, Animal ID for the Animals
And to directly answer your main question, it's better to keep these as separate
Tables. That is called database normalization and is important for query efficiency and elimination of unnecessary data redundancy, but most importantly improved data integrity too. In general, separation of concerns should be split into separate