Konstantin,
I am performing some benchmarking and testing of sequoia 2.10.2 with
Postgresql 8.1. During these experiments, I found some problems with
BIT(n) data type, which is extensively used in our database. It is
looks like sequoia reduce this type to Boolean.
Sequoia retrieves data using ResultSet.getObject(). So we return
whatever the database returns.
Is it possible to process BIT(n) in the way similar to
org.postgresql.driver (correct string representation of the BIT(n) can
be obtained with ResultSet.getString) with sequoia?
It is probably wrong to access a BIT(n) column using
ResultSet.getString(). Anyway, Sequoia behaves as follows:
- if ResultSet.getObject() returns byte[], we decode the byte array
using ResultSet metadata encoding information (see DriverResultSet line 740)
- else we simply return ResultSet.getObject().toString()
Could you tell us what the output looks like when using PostgreSQL and
when using Sequoia?
Why are you using a BIT(n) data type?
Thanks for your feedback,
Emmanuel
--
Emmanuel Cecchet
Chief Scientific Officer, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
