Posted by Roy Harvey on 01/22/07 18:35

On 22 Jan 2007 06:53:36 -0800, "Denis" <k9kondop@hotmail.com> wrote:

>What do you mean it "requires either three columns" ? I didn;t come
>across any such info. What do you mean exactly?

If you want three different languages, without using UNICODE they have
to go into different columns or tables. Three languages, three
columns.

>what I want to do is the following:
>
>
>TABLE A
>---------------
>
>Col1 (English) , Col2(Greek) , Col3 (Chinese)

Three columns.

>where....
>English: Default Collation
>Greek: GREEK Collation
>English: CHINESE Collation (or Unicode)

I assume that last line was supposed to say Chinese: CHINESE.

>Since I can define collation for the 3 different columns, The question
>is: Do i define the chinese/greek columns as UNICODE, or as Chinese
>& Greek respectively? I was thinking the later, because the data
>will take up less space and I will also have more room in the fields.
>What do you think?

If you need English AND Greek AND Chinese, all at the same time, you
might as well use the language specific collations if they have what
you need. If you only need one language on any single row, just using
one column with Unicode will cover all three languages along with
countless others.

One other reason for using Unicode would be that if a fourth (or fifth
or sixth) language becomes necessary there are no database changes.

Roy Harvey
Beacon Falls, CT

[Back to original message]