Personally I would keep a table for the translations.
Some identifier for what it is, and then and id for the language.
So if something doesn't exist in one language you know about it and can default to another language.
It also makes it easier to add new languages in my opinion.


somthing like:

artist_id  | 1234
content | bio
language | english

artist_id  | 1234
content | bio
language | french

artist_id  | 1234
content | bio
language | german

You can index the 3 columns together.

Could also simply be 2 field that makes it a bit more vesatile
content and language

bio_1234
english

bio_1234
french

description_1234
spanish



Ligaya Turmelle wrote:

Looks good to me but I'm a relative beginner. Maybe another option - make Spanish, English, and German tables, then link those to the main table. This however can slow you down if you are doing multiple reads of the various tables.

Respectfully,
Ligaya Turmelle


Graham Anderson wrote:

I have a mysql db that contains tables with multiple language fields
for example...
Artist_id   'PK'
Artist_name
Artist_pictLink
Artist_purchaseLink
Artist_bio_Spanish
Artist_bio_English
Artist_bio_German

I have other tables with a similar layout...Is this needlessly complicated ?
track_id 'PK'
Artist_id 'FK'
track_name_Spanish
track_name_English
track_name_German
track_path
track_versionTotal
track_purchaseLink
track_pictLink


Is there a better way to deal with tables that need multiple language fields...like creating another Db for that language ?

trying to get the design down before I end up with a huge headache...

many thanks





--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to