Hi John,
Thanks, that's what I had thought. This PGobject seems to be the PostgreSQL's JDBC driver's default dump for all sorts of vendor-specific types.
I suspect the way forward for jOOQ here is to
- Introduce support for a new SQLDataType.JSON type
- Include a default, ASL 2.0 licensed JSON implementation in jOOQ (preferably one that implements javax.json)
- Allow for overriding this implementation through converters
This solution should also enable JSON storage in other databases, that do not natively support this data type.
Cheers
Lukas