Oh no, not Unicode again

[Carsten Friehe]

Hi Ruslan!

>-- Classic still important ?
>   or Carbon is enough ?

For me only Carbon is important. I will never work with Classic again. :-)

>   classic can do Unicode work ?

It is not as easy, I think.

>-- show we have the same and only
>            String and VarChar fields
>
>   with addition of 'encoding' parameter?
>   although this way looks to be hard for UTF16

For me it would be enough to have the "old" fieldtypes with addition of
encoding. Although I am using UTF-8 strings in a Valentina database to
store my information. If I am now searching or sorting everything is fine.
I only have to manually set the encoding of the strings when I am
extracting them from a cursor. That's all I have to do. So for me it would
be enough that the strings of a cursor are getting an encoding and I don't
have to set it on my own.

>-- or we should get new 2 fields
>
>            UString
>            UVarChar

I would not prefer this.

>    how other dbs do this ?

I don't know. The last years I had nothing to do with databases except
Valentina. Before I have worked many years with Oracle.

>Just want to hear what you know about this?

I hope it is enough. :-)

Carsten