Pupeno <[EMAIL PROTECTED]> wrote on 01/26/2005 11:48:59 AM: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > There where two cases where I have roles: > How an artist participated in a song (creating the lyrics, creating the > musici, etc, etc) and how an artist participates in a group. > Do you think that enums are good for this kind of things ? or another table ?
I prefer 1 table per association. If I need to associate people (Artists table) to Recordings (song+group+...) as Engineers, I would create a table called Engineer to store that relationship. > If in another table, how would you manage translations (that is, the system > is multilingual), having the translations in that table, or another table ? > or what ? Proper names (groups, artists, albums, etc.) do not need to be translated. Jimi Hendrix is Jimi Hendrix in Spanish, Thai, German, or Swahili. It's the other names (roles, relationships) that shift from language to language. It's rather simple to have a "master" table in one language and translation. Really, the topic of "internationalization" is something you need to research on your own as it really doesn't apply well to this list. > Thank you. > - -- > Pupeno: [EMAIL PROTECTED] - http://www.pupeno.com > Reading Science Fiction ? http://sfreaders.com.ar > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.6 (GNU/Linux) > > iD8DBQFB98n+fW48a9PWGkURAjlAAJsEMwnQDJOqcLMFrSdm6FrLJym6wACdHQxp > XRfhhyEP1ccRuPEqh5f6rqM= > =CzC2 > -----END PGP SIGNATURE-----
