2017-11-16 9:38 GMT+01:00 Pavel Finkelshtein <[email protected]>:
> Hi Lukas, > > One of the problems with these things is that they are very poorly >> standardised, and it will thus be rather difficult for jOOQ to standardise >> on such an API >> > > If I understand problem correctly, JSONB is standartized not by SQL > standart, but by Postgres itself. So it should be possible to create > custom type (PostgresJson for example), which will have it's own custom > functions. > Yes, that would absolutely be possible. Having said so, if this is about a data type binding, it would be really super simple to introduce your own binding (or write a library that you share on GitHub), which can bind any third party JSON library to JSON(B) in PostgreSQL: https://www.jooq.org/doc/latest/manual/sql-building/queryparts/custom-bindings > It was quite predictable. I'm fully agree, that this is not high-priority > feature, remembering that Postgres customers are not paid ones. It was just > idea > Oh, we have quite a few paying customers that use jOOQ with PostgreSQL. But just because they're paying doesn't mean we add every feature that has ever been requested if it doesn't fit the roadmap and the priorities of all of our customers / users :) Again, the main reason why we haven't done this yet is not that PostgreSQL is available from the jOOQ OSS Edition, but because it is really difficult to make the right decision that works for everyone, when it comes to binding JSON. We don't want a PostgreSQL specific solution here. Oracle, SQL Server, DB2, MySQL also support JSON, and the solution would have to work for everyone. Thanks, Lukas -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
