I see. Thank you very much. But I have come up
another question. For the language-dependent
information, there is a code to differentiate each
record, and every column has the same language. What
if I expand my web site, allowing customers from
different countries lookup their orders. How do I
record their information if I allow them to register
their info in their languages? For example, I will
have customer_id and customer_name. How do I record
customer_name? Is it a good practice if I create
every language a column, with customer_id as a
relation?
--- "M. Bastin" <marcbastin@mindspring.com> wrote: >
>Thanks for your idea. What if I give every
> language a
> >table for title and description, and use the code
> as a
> >relation? And one more table for the code, price
> and
> >photos. Please criticize!
>
> In my opinion, it's not good practice to create a
> table per language.
> This will very likely get you into trouble (or, in
> other words,
> you'll have to do much more work), when you want to
> add or remove a
> language afterwards.
>
> Using only two tables is what I'd do: one for the
> general
> information, and one with the language-dependent
> information. For
> every single record in the general table, there will
> be several
> related records in the language table.
>
> Whenever you'll need to retrieve information, you'll
> only need the
> code, and the language of the user, to find the
> right product
> description. You won't need to hard-code a lookup
> in some separate
> 'per-language' table.
_______________________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com.hk address at http://mail.english.yahoo.com.hk
