MySQL One Column, two Foreign Key options -


I have a database set up, it has two tables, with a event containing a Event_ID and Places with Venue_ID . These two tables have slightly different structures (events date and venue_name are not places) I have details of both events and places, which share the same structure. Can there be a description table, which can either refer to a event_id or space_id , or is it better to keep it separate? Or is there a third option?

places + developments do not have many details (referencing comments)

I'm not sure what your institutions are trying to do, but I (a native English speaker), a "phenomenon" is very different from a "site". An "event" is something that happens at a particular point in time and place. "Participants" can sign up for an "event" A "venue" is a special place. These are very different bodies.

There is a connection between them. As Alvaro points out in his comment, there is not a suitable feature for venue_name event . venue_id is a suitable attribute, creating a link between the table.

The answer to your question is that you can put the details in a table, but generally it is usually (in most cases) to include the details of different entities in a table, generally, You add a description column to the table, where you want that attribute.

There are some situations where such a table can be desirable if you are creating a multilingual database application and description can be shown to some users, you can translate You may want to store all such stars in the same table.

Comments

Popular posts from this blog

Pass DB Connection parameters to a Kettle a.k.a PDI table Input step dynamically from Excel -

multithreading - PhantomJS-Node in a for Loop -

c++ - MATLAB .m file to .mex file using Matlab Compiler -