Indeed, a fork of 3.10 would probably lead to you sticking to 3.10, as 3.11 changed quite a bit of its internals, especially in the area of data type binding. Upgrading your changes might be tedious - but doable.
Right now, I indeed don't see enough traction for Snowflake to add and maintain a dialect in jOOQ... 2018-06-05 17:44 GMT+02:00 <[email protected]>: > I was thinking about snowflake, another data warehouse solution. > > That's a fun little catch-22 for us. We could fork 3.10 to add local > support for snowflake but know that we won't be able to contribute it to > you, or use 3.11 for support of teradata, but can't do both. > > > On Monday, June 4, 2018 at 1:45:13 PM UTC-6, Lukas Eder wrote: >> >> Hi Bear, >> >> A lot is required :-) >> >> In the early days of jOOQ, adding support for a new database was rather >> simple - maybe 2-3 days' worth of effort for me, or perhaps 1 week for a >> contributor. >> >> Times have changed. jOOQ 3.11 will add support for 4 new databases: >> Aurora MySQL & PostgreSQL Edition, SQL Data Warehouse, and Teradata. The >> latter have been quite a hassle to get right and took quite a while to >> implement, both with still quite a few "known limitations" (e.g. no stored >> procedure support in Teradata yet). >> >> There's a lot of work getting the (closed source) integration tests to >> run, keeping track of all the hundreds of little edge cases that they >> contain in the meantime. Which is a good thing. This means that jOOQ has >> matured a lot and it's become more quite difficult to write a query that >> breaks jOOQ (e.g. some funky edge case where a correlated subquery uses >> offset / limit, but omits order by, along with some nested union operations) >> >> Having said so, I don't think it's reasonable for a contributor to add >> support for additional databases at this point, let alone for us to accept >> a PR and maintain it. Unlike JPA, for example, jOOQ really supports >> (almost) the entirety of the SQL language and has to emulate all sorts of >> features in all sorts of dialects. Here are some examples: >> https://blog.jooq.org/2018/03/13/top-10-sql-dialect-emulatio >> ns-implemented-in-jooq >> >> It has become very difficult to get this right, and there are only few >> databases left where the market is big enough to justify the effort of >> adding an integration (Teradata was one of them) >> >> Hope this helps, >> Lukas >> >> 2018-06-04 16:57 GMT+02:00 Bear Giles <[email protected]>: >> >>> Out of curiousity what is required for support of new databases? I know >>> the database-specific packages are pretty thin but I would imagine there's >>> quite a bit of testing distributed throughout the package hierarchy. >>> >>> Bear >>> >>> -- >>> 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. >>> >> >> -- > 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. > -- 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.
