Hi Pedro,
Thank you very much for your message and for your interest in our translation service. Both the Snowflake and BigQuery dialects are work in progress for the upcoming jOOQ 3.15 dialect, with BigQuery being almost ready, while Snowflake still requires quite a bit of work.
The library's upcoming 3.15 version (available already to paying customers) has one key feature that will definitely improve the experience of the translation use-case: An SPI that allows you to hook into the parser and translate table, column, and predicate expressions that may not yet be supported out of the box:
https://www.jooq.org/doc/dev/manual/sql-building/sql-parser/sql-parser-listener/
However, from our experience, 50% of the times when users find limitations in the parser, they are very easy for us to fix really quickly, so if you find any issues, just let us know either here or through the issue tracker: https://github.com/jOOQ/jOOQ/issues/new/choose
Please let me know if I can be of any further assistance and I'll be very happy to help,
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
jooq-user+...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jooq-user/557a4fc5-2fb3-4adf-baa8-6b73c8d0bb06n%40googlegroups.com.
Hi Pedro,
A quick check reveals that the DATE_TRUNC function isn’t yet supported for BigQuery. I’ll look into this soon, this week. This is a great example where you could work around the current limitation using a ParseListener, as I mentioned in my previous email.
The cast is translated correctly.
The GROUP BY 1, 2 semantics (referencing projected column expressions by index or alias from GROUP BY) is something we’ve been asked for a few times, also in the context of translating Teradata SQL to other RDBMS: https://github.com/jOOQ/jOOQ/issues/11820. I can’t promise this for the upcoming week, but we’re very keen on getting this to work for jOOQ 3.15.
I hope this helps,
To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/821fa0b2-aaa3-4a0c-a0eb-321bcb648370n%40googlegroups.com.
Hi Pedro,
When you say "::" doesn’t work for bigquery, do you mean it doesn’t work on https://www.jooq.org/translate/ ? As far as I can tell, that’s not a problem:
Have you tried it?
Yes, DATE_TRUNC doesn’t work yet, indeed. Regarding your purchasing decision: I will be happy enrol you for an extended trial license to work with the latest jOOQ 3.15.0 SNAPSHOT version, which you will be able to get from here, no strings attached: https://www.jooq.org/download/versions
I’ll reach out to you directly via a private email for an extended trial license key.
Best Regards,
To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/d7d47ccc-54dd-4557-9cdd-f602141a5a3bn%40googlegroups.com.
Hi Pedro,
For the record, I’ve just implemented DATE_TRUNC and DATETIME_TRUNC support for BigQuery, which will be available with the next nightly builds.
I’ve checked again, it seems that BigQuery supports GROUP BY <select column indexes> as well, so https://github.com/jOOQ/jOOQ/issues/11820 won’t be necessary for your query to be translatable.
Moving forward, in order to evaluate jOOQ, I think it would be best if you work with the extended trial license I’ve sent you and assemble a catalog of requirements. Again, things like that DATE_TRUNC() support are very easy to add, and we’ll usually just do it without any additional costs.
Best Regards,
Lukas
To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/AM7PR03MB6610388C835ED1FBE1F0287D9F249%40AM7PR03MB6610.eurprd03.prod.outlook.com.