Re: [Modeling-users] working in unicode?

[Yannick G. <ygi...@yg...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 22 April 2003 06:38, you wrote:
> One step up, two steps back... but i guess support for this will
> eventually come.  If i understand correctly with postgres, you can
> send a select query in unicode directly, and a case insensitive
> condition should work... But the middle layer does not support this
> unfortunately...

Ah well...

But you were wright, the lack of case-insensitive search is far less
evil than the field length expansion when working with utf-8 encoded
data.  Shouldn't Modeling allocate enough space to store 8 char of any
language if I say that I want 8 chars for some property ?

It should not be the application programmer's job to know all the
technicalities of utf-8 encoding.

That's one of the use we have for comments now, we say the field
intended length and we put the "physical" length in the model...

IMHO, the is a ugly hack.

- -- 
Yannick Gingras
Coder for OBB : Overlooked Biogeographical Backseat
http://OpenBeatBox.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+pSUMrhy5Fqn/MRARAqhIAJ4w7thSD8RZ033RdyfCKh4UsmDxhACeLVXU
BeTPC1XmC+P6/KSzsDkRqEU=
=qabP
-----END PGP SIGNATURE-----