On 28-6-2012 18:56, the_a_rioch wrote:

>
>>> the developers of TS
>>> don't need to do anything. You just need to include the charSet or
>>> encoding property in the JDBC url specified in the
>>> hibernate.connection.url property.
>>
>> Yes, i thought of that and would try it.
>
> It seems to work, even built-in initialization works.
> Yet... the fact that they did not identified problem hints at broken expectations...

You said they use Linux themselves. Under Linux the default system
encoding is usually UTF-8. In that case the NONE charset applied by
Jaybird will work transparently for them if the database characterset is
UTF-8 as well. With NONE, Jaybird will use the system encoding to
convert between Java strings to bytes.

However when running on Windows, the default characterset for you is
probably WINDOWS-1251. In that case Jaybird will use that characterset
to convert between Java strings and bytes. The problem now is that those
bytes may contain byte combinations which are not valid UTF-8 so upon
storing in the database a transliteration error will occur.

Mark
--
Mark Rotteveel