UUID dual-way representation problem about sql2o HOT 6 CLOSED

I'm not sure I understand the issue. Is the problem that the UUID converter doesn't work across databases?

from sql2o.

every time you pass UUID to PreparedStatement you need uuid2bytesArray translation
every time you read UUID from ResultSet you need bytesArray2uuid translation
the problem: for the same UUID MSSQL and Oracle has different byte order in bytesArray.

from sql2o.

Ahh gotcha. This sounds like a great candidate for Quirks.

from sql2o.

the probjem is not Oracle vs MSSQL
the problem is Database with native UUID column type vs Database where UUID is stored just as byteArray

from sql2o.

Any progress on this? I have a postgres db with a UUID and no idea how to use it with sql2o. I get a NPE on addParameter("uuid", UUID.randomUUID()) and addParameter("uuid", UUID.randomUUID().toString())

from sql2o.

After the introduction of bidirectional converters, a UUID converter will convert both parameters and results. So the specifics of this issue has been fixed for some time now. The UUID datatype works out of the box for Postgres, without any specific converter. @ftomassetti I think you have a different error? Check out this postgres test.

Instead of keeping this issue open, I have created new issues to add UUID converters for Oracle, MsSql and DB2.
#195 #196 #197

from sql2o.