| Subject | Firebird 2 and UTF-8 field length in chars or bytes? |
|---|---|
| Author | mailmur |
| Post date | 2004-12-19T16:00:51Z |
I tried to find infos about UTF-8 or any unicode encoding work
properly in next releases. Current version 1.5.x allow storing
overlength values.
It uses a number of bytes, instead of number of _chars_, so varchar(3)
column may actually have max six characters stored in it.
Another issue is UCASE/LCASE functions working properly with UTF-8
columns.
properly in next releases. Current version 1.5.x allow storing
overlength values.
It uses a number of bytes, instead of number of _chars_, so varchar(3)
column may actually have max six characters stored in it.
Another issue is UCASE/LCASE functions working properly with UTF-8
columns.