Re: Multiple tables refer to one -To use foreign keys or not?

Adriano Varoli Piazza wrote:

As one of my first encounters with SQL (The RDBMS used is MySQL 5.1),
my colleague and I have designed the following (it's a part of a
catalog system for a museum):
We have an "attachments" table, which can refer to "works_of_art",
"people", "reproductions" (Let's say, more than three tables). So a
work of art can have attachments, a person can have a different
attachment, etc.

To be able to relate each object to its eventual attachments, one
solution I imagined is to put N foreign keys from each of the tables
referred in attachments (if my use of the verb refer is incorrect,
please do point it out). Let's say that, for now, there are no fields
exclusive to any of the referred tables, so creating different
attachment tables is not the best obvious choice.

The alternative solution we came up with was to use two fields in
"attachments" to identify the relations: one with the id of the
referred table, and one with the "type". So 'works of art' would be 0,
'people' would be 1... The reasoning behind the decision was that my
colleague felt that too many fields would remain empty with the first
solution, and that adding a new type of "attachee" was simpler/more
efficient than adding a new foreign key.

This solution doesn't strike me as the best. We want to use cakephp to
build the app that will use the database, and while this solution
would eventually work with some manual labour, I feel it grates
against it when the rest of the design does not. Since my knowledge of
SQL is tenuous at best, I wanted to listen to some informed opinions
about this before arguing again.

By all means, if this is a WTF, point it out, the reason, and possibly
an alternative.

Saludos,
Adriano

I will cite Date's _Principle of Incoherence_ and ask whether you are re-inventing EAV, yet again?
.

Relevant Pages

  • Re: Multiple tables refer to one -To use foreign keys or not?
    ... To be able to relate each object to its eventual attachments, ... So 'works of art' would be 0, ... colleague felt that too many fields would remain empty with the first ... Database design is not about making it easy to do correct things so much as ...
    (comp.databases.theory)
  • Multiple tables refer to one -To use foreign keys or not?
    ... As one of my first encounters with SQL, ... To be able to relate each object to its eventual attachments, ... colleague felt that too many fields would remain empty with the first ... against it when the rest of the design does not. ...
    (comp.databases.theory)
  • Re: Multiple tables refer to one -To use foreign keys or not?
    ... To be able to relate each object to its eventual attachments, ... So 'works of art' would be 0, ... colleague felt that too many fields would remain empty with the first ... The general principle is: don't put data and metadata side by side in the ...
    (comp.databases.theory)
  • Re: watering system, second attempt.
    ... > CMOS ICs and a mosfet to switch the coil. ... > design i've come up with. ... but then a chip failed and i'm waiting to get another one. ... html mail or attachments will go in the spam ...
    (sci.electronics.basics)
  • Microsoft Outlook 2003 - Forms
    ... I have designed myself a form for a mail message that I will be using all ... forms library form, can you not design it to allow you to add attachments to ...
    (microsoft.public.windowsxp.security_admin)