I would make 2 tables, a product table and a language table... It would look
like so:
Product ID | product name | manufacturer | etc
Then a language table that looks like:
Language ID | Product ID | product description | etc
Then you won't be replicated your 11 columns since they are not in the
product table anymore.. If there are 100 products, and 1 language then there
will be 100 records in the product table and 100 in the language table. If
there are 2 languages then there will be 200 in the language table.
This method means you will be able to expand your language endless... and I
don't think your DB Server will be slowed down too much by this, since u can
pull this all of with 1 query.. something like (from memory)
SELECT tblProducts.name, tblLanguage.Description FROM tblProducts,
tblLanguage WHERE tblProducts.productID=tblLanguage.productID AND {some
other query}
Hope this helps
Andrew
----- Original Message -----
From: "Wilbert Enserink" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 15, 2002 12:33 PM
Subject: [PHP] db design
> hi all,
>
>
> I need some tips on database (mySQL) design.
> The problems lie in languages. I'm gonna make a e-commerce webiste. it's
> rather big (in my terms/experience). The website should be expandible
easily
> with regard to languages/translations.
>
> My biggest table with product descriptions has 43 columns. Other tables
> include a list of FAQ's, manufacturers and so on.
>
> What do you think I have to do? Make a new table for each language, or
> define more columns for each language within a table? What is normal in
> this, also with regard to doing queries?
>
> e.g. In the table with 43 columns, there are 11 columns which are the same
> for each language (product name, manufacturer and so on) The other columns
> will depend on language (like product description).
> --If I use a seperate table for each language than there is double info
(no
> normalization with regard to the 11 columns)
> --If I use more columns, than I have 32 columns extra per language. If I
> make 10 translations, then this table will reach over 10x32=320 columns.
>
> I need somebody who can give me overall info on this, or shine a broad
light
> on my Q. Does the db design has a large influence on flexibility with
regard
> to future expanding? And how about query times (response) on a server. I
> don't want it to get too slow....
>
> Well I think, you know my point now,
>
> any info is much appreciated!!
>
>
> thx in advance,
>
> Wilbert Enserink
>
>
> -------------------------
> Pas de Deux
> Van Mierisstraat 25
> 2526 NM Den Haag
> tel 070 4450855
> fax 070 4450852
> http://www.pdd.nl
> [EMAIL PROTECTED]
> -------------------------
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
