Martijn Tonies escreveu:

>
> Right, I've just experimented with sending SQL as UTF8 to Firebird
> when the database is UTF8

Database charset is used *only* when you are creating fields or
parameters without an explicit charset.

> and that seems to work, including table
> names and so on. Would this be the correct way to go then?

It depends on what is "SQL as UTF8". Encoded in UTF-8? Then yes, if you
use UTF8 connection charset.

> I'm decoding, for example, SQL Plan and exception messages.
>

Plans are transliterated to the connection charset since v2.1 or v2.5, I
don't remember. Exceptions are only transliterated when you use dynamic
texts (i.e., exception x 'text'), because stored text is in NONE charset.

> Should I also do value decoding or is that handled by the OS/Firebird
> client?
>

It should be automatically be in the connection charset.

>> Martijn, there may be problem with such types of names, AFAIR some
>> problem fixed recently may be only fixed in v2.5. If you found new ones,
>> please tell us, but when using things correct. :-)
>
> I'm not telling you about new things, I'm asking for help!! I do not -know-
> how
> to use this correctly, which is why I'm writing to "firebird-support" and
> not to
> "firebird-devel".
>

Sorry, I may have not said what I want. I mean you're using a thing with
has a potential to be problematic. If you found real problems, I'm glad
to know them.


Adriano