On Mon, Jun 22, 2020 at 7:31 PM Ryan Wisnesky <[email protected]> wrote:
> What's the use case of this transformation? > > > I’m trying to use JOOQ as a “universal parser” for a very simple > select/from/where fragment of SQL with a simple abstract syntax, but across > a bunch of vendors at once. But perhaps this is the same problem as the > problem above - how to insert new variables in from clauses. > But jOOQ's out of the box parser / renderer can already do that. It can parse this simple syntax (or even more complex syntax), and then transform it to whatever dialect is currently supported. You seem to want to have some (cosmetic?) transformations in the generated SQL, which are out of scope for what jOOQ can do right now. Of course, we can add these things eventually, but they will take time to implement. My question here is less related to the question *what* you want to achieve, but to the *why*. Why do you think ANSI joins work less well? Why do you think all columns have to be qualified? Why do you prefer all tables to be aliased? Without understanding the "whys", I don't think I can provide you with the best possible "hows"... 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO6xsCzem48B0FkXoR%3D8KL41drZBf1sN_PiGjvyL9DKFhQ%40mail.gmail.com.
