| Subject | Re: [firebird-support] 60 chars in a 50 field |
|---|---|
| Author | Adriano dos Santos Fernandes |
| Post date | 2005-02-25T15:43:59Z |
This problem was solved with new INTL in this manner:
All existing MBCS is marked as CHARSET_LEGACY_SEMANTICS.
CHARSET_LEGACY_SEMANTICS mean that the current behaviour remain.
In current INTL UTF8 is a alias to UNICODE_FSS.
When you create a field and inform "character set utf8" the charset stored in system tables is UNICODE_FSS.
In new INTL UTF8 is not a alias to UNICODE_FSS, it's a new charset (it's not CHARSET_LEGACY_SEMANTICS) without the problem mentioned.
Adriano
All existing MBCS is marked as CHARSET_LEGACY_SEMANTICS.
CHARSET_LEGACY_SEMANTICS mean that the current behaviour remain.
In current INTL UTF8 is a alias to UNICODE_FSS.
When you create a field and inform "character set utf8" the charset stored in system tables is UNICODE_FSS.
In new INTL UTF8 is not a alias to UNICODE_FSS, it's a new charset (it's not CHARSET_LEGACY_SEMANTICS) without the problem mentioned.
Adriano