On Fri, Oct 27, 2017 at 1:23 PM, Lukas Eder <[email protected]> wrote:

>
> Well, for starters, that DatabaseMetaData API is really not reliable,
> unfortunately. The jOOQ code generator does not rely on it to reverse
> engineer your database, we run our own queries against each databases'
> dictionary views.
>
> Also, behind the scenes, DatabaseMetaData runs a query (how else would it
> fetch the tables?), but that query is not governed by any of jOOQ's
> execution lifecycles, which raises many new questions about how this
> interaction would be perceived by jOOQ API users.
>

Noted. I only need "getTables()" , and I suspect it is reasonably well
supported. Totally undestand JOOQ's extensive support of all kinds of stuff
that should have been in the Drivers.



> I'm not sure what you mean by data modeling tooling. The code generator?
> In that case, no: The @Support annotation annotates the DSL API to tell
> users which SQL clauses are available in which SQL dialects. For instance,
> you could see that createTableIfNotExists is available for these dialects:
>
> @Support(value={DB2,FIREBIRD,H2,HSQLDB,MARIADB,MYSQL,
> ORACLE,POSTGRES,SQLITE,SQLSERVER,SYBASE,VERTICA})
> CreateTableAsStep<Record> createTableIfNotExists(Table<?> table)
>
>
I meant the POJO conversion support. In my case, JOOQ is not given any
types to inspect and nowhere to put any annotations.


Is there a way to get hold of the current connection?  I think I can only
>> do acquire() on the ThreadLocalConnectionProvider but Reflection on the
>> ThreadLocalTransactionProvider, but that is nasty and would like to
>> avoid if there is a better way.
>>
>
> Yes, you can use DSLContext.connection() and connectionResult():
>

Thanks.

-- 
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to