Do you have any specific concerns related to casts? you said you wanted to
> avoid "points of divergence," but that doesn't sound like you ran into any
> actual issue.
>
> Best Regards,
> Lukas
>
> On Wed, May 1, 2024 at 11:41 AM Ahmed Ghanmi wrote:
>
>&g
We are trying to test parsing with meta lookups. However, we had two issues
:
- jOOQ was attempting to fetch metadata with every connection even when the
DSLContext is reused. Are we missing something in the settings?
- it seems that jOOQ isn't identifying tables/columns unless the
identifiers
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
specifically?
>
> Best regards,
> Lukas
>
> On Mon, Mar 18, 2024 at 3:54 PM Ahmed Ghanmi wrote:
>
>> Hello Lukas,
>>
>> In our Oracle->PG migration, we are using JOOQ's ParsingConnection to
>> translate between dialects.
>>
>> Similar to
Hello Lukas,
In our Oracle->PG migration, we are using JOOQ's ParsingConnection to
translate between dialects.
Similar to https://github.com/jOOQ/jOOQ/issues/11757, we are facing issues
with Oracle's NULL and empty string equivalence.
The assumption is prelevant across the codebase as we have
