Hi Kiran,

Thanks for your message.

I'm sorry, I don't understand what's not working. It's always a good idea
to accompany your requests with actual code examples, ideally in a way for
others to be able to reproduce the issue you're having.

When creating an issue on our issue tracker, we suggest creating an MCVE
(Minimal, Complete, Verifiable Example) from our template here:
https://github.com/jOOQ/jOOQ-mcve. That might not be necessary, but is a
guaranteed way to have reproducible examples, irrespective of whether this
is about a bug or a support request.

Best Regards,
Lukas

On Wed, Jun 15, 2022 at 8:45 PM 'Kiran Kumar Thungala' via jOOQ User Group <
[email protected]> wrote:

> Hi team,
>
> I am trying to solve double quotes around alias with JOOQ version -
> 3.14.15 and found following issues.
>
>    - JOOQ not honoring the value when we explicitly set `Settings` of
>    RenderNameStyle to 'RenderNameStyle.AS_IS'. But works fine when add system
>    wide settings via '/jooq-settings.xml'.
>    - Deprecated RenderNameStyle's alternative RenderNameCase is not
>    working with either explicit `Settings` or system wide settings
>    via '/jooq-settings.xml'.
>
> Thanks,
> Kiran T
>
> --
> 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/502c7d9b-927d-4521-97ce-6fefaf478d9an%40googlegroups.com
> <https://groups.google.com/d/msgid/jooq-user/502c7d9b-927d-4521-97ce-6fefaf478d9an%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAB4ELO4URzyR-FFWo5j6KsKJ%3DZSvxoW9iUAuzSYkhQxTTbrOBg%40mail.gmail.com.

Reply via email to