Subject | Re: [firebird-support] Charset for identifiers and check constraints? |
---|---|
Author | Kjell Rilbe |
Post date | 2008-06-19T05:24:15Z |
Helen Borrie wrote:
defined by the connection, and then FB would transliterate any parts of
it as appropriate:
...check ("Användare" <> 'abcåäö')...
...-------><-------><----><----><-...
1 2 3 4 5
Parts 1, 3, and 5 would be transliterated to plain ascii.
Part 2 would be transliterated to UTF8.
Part 3 would be transliterated to the charset of "Användare".
Or is it actually the case that this transliteration should be made by
the client? (Would seem rather odd...)
Just trying to understand what's going on.
Thanks,
Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64
> Not "inconsistent" from the Firebird p.o.v., though. You (and the tools)But shouldn't the client send the DDL expression/query in the charset
> must distinguish between metadata and data, specifically in DDL that
> provides text constants in expressions defining constraints, computed
> columns, domains, etc., and also user-defined triggers and stored
> procedures that have been migrated without recompiling.
defined by the connection, and then FB would transliterate any parts of
it as appropriate:
...check ("Användare" <> 'abcåäö')...
...-------><-------><----><----><-...
1 2 3 4 5
Parts 1, 3, and 5 would be transliterated to plain ascii.
Part 2 would be transliterated to UTF8.
Part 3 would be transliterated to the charset of "Användare".
Or is it actually the case that this transliteration should be made by
the client? (Would seem rather odd...)
Just trying to understand what's going on.
Thanks,
Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64