You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike other, simple SQL libraries, jOOQ supports a vast amount of SQL features on most of these dialects, and allows for emulating them if not supported, meaning that integration testing has grown complex over the years. We believe that the most important dialects are already supported, according to this popular ranking website: https://db-engines.com/en/ranking
Sponsorship
But maybe, your preferred SQL dialect is still not supported? If you're a vendor or customer of a new SQL database product, and would like jOOQ to support your dialect as well, please reach out to sales@datageekery.com to see if we can start a sponsoring project to help us cover for our efforts in maintaining your dialect. Typical terms include:
Support for most jOOQ features, including e.g. SQL generation, stored procedures, code generation, etc.
Support for the RDBMS for the next 5 years (unless the RDBMS changes significantly, or removes SQL support, etc.)
Inclusion of the dialect in the commercial or open source edition for everyone to use, depending on the database product
SQL-ish dialects
From time to time, someone asks us to support a "SQL" dialect like KSQL
Our stance here is that those dialects aren't really SQL and it wouldn't really make sense to support them in jOOQ. Full rationale can be seen here: #11903 (comment)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Q: Will SQL dialect X be supported by jOOQ?
A: It might be :)
Current dialect support
jOOQ supports 30+ SQL dialects, see:
https://www.jooq.org/download/#databases
Unlike other, simple SQL libraries, jOOQ supports a vast amount of SQL features on most of these dialects, and allows for emulating them if not supported, meaning that integration testing has grown complex over the years. We believe that the most important dialects are already supported, according to this popular ranking website:
https://db-engines.com/en/ranking
Sponsorship
But maybe, your preferred SQL dialect is still not supported? If you're a vendor or customer of a new SQL database product, and would like jOOQ to support your dialect as well, please reach out to sales@datageekery.com to see if we can start a sponsoring project to help us cover for our efforts in maintaining your dialect. Typical terms include:
SQL-ish dialects
From time to time, someone asks us to support a "SQL" dialect like KSQL
Our stance here is that those dialects aren't really SQL and it wouldn't really make sense to support them in jOOQ. Full rationale can be seen here: #11903 (comment)
Beta Was this translation helpful? Give feedback.
All reactions