| Subject | Re: [Firebird-Java] OCTETS as binary (and another problem with CachedRowSetImpl) |
|---|---|
| Author | Mark Rotteveel |
| Post date | 2012-07-19T14:21:11Z |
On Thu, 19 Jul 2012 13:45:16 -0000, "Fabiano"
<fabiano@...>
wrote:
in Jaybird 2.3 (see section 'Handling (VAR)CHAR CHARACTER SET OCTETS as
(VAR)BINARY type' in the releasenotes), the change was too complex to
consider for Jaybird 2.2.
You could check if providing connection property octetsAsBytes in your
connection string is sufficient to make CachedRowSetImpl use it correctly
as that property will make the ResultSetMetaData report the column as
(VAR)BINARY.
Mark
<fabiano@...>
wrote:
> Hi all!The way Jaybird handles (VAR)CHAR CHARACTER SET OCTETS is going to change
>
> It seems Jaybird is treating "CHAR/VARCHAR CHARACTER SET OCTETS"
> internally as Strings. I personally don´t think it is correct, as OCTETS
> are used to store binary data. What do you think about this?
>
> I tried to look at Jaybird code some months ago to offer a fix, but at
> that time, it seemed to me it would need a bunch of changes to make it
> work.
in Jaybird 2.3 (see section 'Handling (VAR)CHAR CHARACTER SET OCTETS as
(VAR)BINARY type' in the releasenotes), the change was too complex to
consider for Jaybird 2.2.
You could check if providing connection property octetsAsBytes in your
connection string is sufficient to make CachedRowSetImpl use it correctly
as that property will make the ResultSetMetaData report the column as
(VAR)BINARY.
Mark