For the record, more recent jOOQ versions have added support for additional ResultSet fetching methods, such as DSLContext.fetchOne(ResultSet, Field<?>...), which can be used to pass bindings to the internal Cursor.
jOOQ 3.12 also implements ResultQuery.coerce(Field<?>...): https://github.com/jOOQ/jOOQ/issues/4473 ... and DSLContext.resultQuery(ResultSet): https://github.com/jOOQ/jOOQ/issues/8316 Which can be used to attach bindings to a ResultQuery that is backed by a JDBC ResultSet I hope this helps, Lukas On Monday, November 20, 2017 at 11:11:35 AM UTC+1, Lukas Eder wrote: > > 2017-11-17 17:41 GMT+01:00 <[email protected]>: > >> My schema is dynamic, so I don't have any table-to-class mappings. And >> it's not possible to set such forcedType in a DSL config, is it? >> > > Unfortunately, right now, it isn't - at least not for your particular > "plain SQL" / "direct JDBC" usage. The pending feature request is here, > I've increased its priority for jOOQ 3.11: > https://github.com/jOOQ/jOOQ/issues/4473 > > If you're willing to patch your jOOQ version, you will be able to > implement the feature directly in org.jooq.impl.MetaDataFieldProvider, > which creates Field<?> and DataType<?> references from JDBC's > java.sql.ResultSetMetaData > > I hope this helps, > 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]. For more options, visit https://groups.google.com/d/optout.
