> > Have you considered exposing or using the JDBC escapes like > TIMESTAMPDIFF and then leave it up to the driver to provide the > translation? That does assume that drivers implement those JDBC escapes, > but it is required for the Java EE support level of a driver.
I really don't like those escapes. 1) They're very poorly supported 2) They're very incomplete (why are there escapes for 1-2 features, but not the gazillion other ones?) 3) They produce SQL that relies on JDBC, which we don't want. jOOQ can be used in other, non-JDBC based tooling, e.g. https://www.jooq.org/translate We're only using JDBC escapes if there is really no other way. E.g. in HSQLDB, some functions are *only* implemented using this escape syntax. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO4z5mhvRTr4wwmaZcFMG554YeMPDkS5DkALDmLQHtZqAQ%40mail.gmail.com.
