Hello Adriano,

> >> Use the correct connection charset for your platform.
> >
> > Which is? :-)
> >
> > I was using UTF8...
> >
> And does Database Workbench works in anything other than Windows? :-)
> Because it's not the charset of Windows.
>
> When you type things as ÅÄÖ in Win32 GUI, and sent it as UTF-8, FB is
> going to interpret it as an array of bytes in UTF-8. Since first
> character has the high bit set to 1, you are telling that this is not 3
> characters, but 2 or 1. And it may not be correctly encoded, so the
> malformed string error.

Right, I've just experimented with sending SQL as UTF8 to Firebird
when the database is UTF8 and that seems to work, including table
names and so on. Would this be the correct way to go then? I'm
decoding, for example, SQL Plan and exception messages.

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

> 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".

> One of the problems (even in v2.5) is that you are limited by the number
> of bytes (and not characters), so depending on the characters you use
> you may be limited by object names of less than 8 characters.

That's not my problem ;-)


Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Sybase
SQL Anywhere, Oracle & MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com