AW: [ic] Use one table for product descriptions in different languages

Daniel Davenport ddavenport at
Wed Jul 13 11:07:29 EDT 2005

>>> racke at 07/12/05 5:56 AM >>>
>Lars Tode wrote:
>>Hi list.
>>Thanks for all of your ideas :)
>>2 Ethan :
>>We used mysql 4.1 as data source. The main encoding is utf8 and the
>>colate utf_bin. The problems you had talked about, are really ugly :(
>>But utf8 and mysql 4.1 including german umlauts is a very interesting
>>story, too ^^
>>2 Kevin :
>>The idea with the shadow tables is great, but I think the handling
>>(always create a new table for each language) is a bit difficult.
>You don't need one table for each language. You can also put all your
>translations in one table, e.g.
>and then:
>Database products MAP description de_DE products_i18n description_de
>Database products MAP description fr_FR products_i18n description_fr
>       Racke

The one drawback being that adding another language == adding another pair of fields.  I'd be happy with that * in fact, i've done it that way in the catalogs where people cared about other languages * but the OP made it sound like it would be a bad thing in his case.


More information about the interchange-users mailing list