Re:I don't want to learn your query language (2018)
by gregopet on Thursday March 11, 2021 @01:49AM
(#26421070)
Another jOOQ fanboy here - it's not just the manual that shows DSL->SQL, you can just .toString() most of jOOQ constructs in your code and get the raw SQL out. In fact, I believe you can just take that .toString() and put it straight into your prepared statement if you don't want jOOQ to run your queries and just use it for query composition.
[ Parent
| on HN ]
Re:I don't want to learn your query language (2018)
by lukaseder on Sunday March 14, 2021 @05:49AM
(#26453963)
Like any toString() implementation, it is meant for debugging. If the object you're calling toString() on is "attachable" (e.g. a Query), then you get the vendor specific string for additional convenience. If you just call substring(a, b, c).toString(), you'll get a generic rendering.
If you always want the vendor specific SQL string, use DSLContext.render(QueryPart)