|Subject||Re: [Firebird-Java] Handling charactersets|
>> Let's stop this discussion here - it is becoming to lengthy. :)Agree.
> I am of the opinion that changing the handling of unspecified
> charactersets in Jaybird is not without (significant) risk. I would
> like to
> propose a gradual change in the way Jaybird handles unspecified
> charactersets. The final goal would be to default to UTF-8 as the
> characterset when no characterset is specified.
> We could introduce this in Jaybird 2.3 as an optional defaultI was thinking about warning as well, however that will be ignored :)
> (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.
Maybe we should simply deny connection?
> This change would be explicitly mentioned in the releasenotes etc.Yes, that is what I was thinking about.
> Jaybird 3.0 we switch this around: using UTF-8 as the default, people
> preferring the old way would need to explicitly specify the
> characterset as NONE. Optionally we may also need to allow for more
> on how one specific connection converts the bytes received when
> explicitly with NONE (eg to allow for conversion and fixes of data
> two connections).