On Tue, 03 Jul 2012 15:49:21 +0200, Roman Rokytskyy <roman@...>
wrote:

>> We could introduce this in Jaybird 2.3 as an optional default
>> (requiring a
>> Java system property to enable it). I would propose we also add
>> warnings in
>> the logs (and maybe a SQLWarning on the Connection, although most
>> developers ignore those) when no explicit connection characterset is
>> selected. This would really be required for the current behavior, but
>> probably also a good idea for the new behavior.
>
> I was thinking about warning as well, however that will be ignored :)
> Maybe we should simply deny connection?

I am not sure I like this, on the other hand it would force the people to
look at their current use of charactersets in Jaybird 2.3. This would of
course not happen with the optional default of UTF-8 (or with the new
default for Jaybird 3.0).

Mark