We are using jOOQ's ParsingConnection to translate queries from ORACLE to POSTGRESQL. We've noticed that jOOQ was automatically adding casts in places where the typing is evident. Suppressing these casts is important to us as we do not want to add any more points of divergence between oracle and postgresql.
1. Is there a way to suppress automatic casting completely when using the parser. If not, are there any plans to implement this option? 2. It seems that activating meta lookups allows jOOQ to type expressions from the schema, which should inhibit much of the unnecessary casts (we have not tested this feature yet). When using meta lookups, in which cases will jOOQ add its own casts ? -- 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/5baa2ecb-f4bf-48ad-805d-e6c79e95f832n%40googlegroups.com.
