Hi Marek,

On Mon, Sep 9, 2019 at 10:16 AM Marek Gregor <[email protected]> wrote:

> Hello Lukas,
>
> thanks a lot for response, I am sorry, I have not noticed the obvious bug
> in my DDL, the reflection warnings deceived me.
>

No worries at all! What jOOQ distribution did you get those reflection
warnings with? There's a known issue in the jOOQ Open Source Edition where
those warnings persist, but they should have been fixed in the commercial
JDK 11 distributions...


> I have not realized that parsing unqualified column names is not so
> straightforward to implement, I think existing state - using qualified
> names is perfectly fine for use.
>

Yes, unfortunately, but rest assured, this is a high priority for us.


> Feature of parsing with meta lookups (.withParseWithMetaLookups(
> THROW_ON_FAILURE)) is perfect for validation of queries without even
> running them, this I think will be killer feature for any reporting tool
> ;). In DslContext.meta() I miss only one thing - possibility to list and
> run stored procedures (org.jooq.Routine) in some dynamic way without static
> generation. But this could be also implemented by me when needed, by
> reverse engineering code of org.jooq.codegen.JavaGenerator#generateRoutines
> in a way to support dynamic calling of routines without code generation ...
>

That is on our roadmap. We might need to implement a few prerequisites
first, including a routine meta model (which is currently mixed with the
actual routine call):
https://github.com/jOOQ/jOOQ/issues/8748

Definitely something we'd like to add soon as well, as we're also going to
support parsing routine DDL statements, such as CREATE FUNCTION and CREATE
PROCEDURE.

Thanks,
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/CAB4ELO7idb5UxrNU8Lr0WAhkdHHaR1ZnaO50JqkLYQzRfxQTSw%40mail.gmail.com.

Reply via email to