I use JOOQ for query generation. The generated SQL is executed using JDBC calls. The resulting JDBC resultset is processed using JOOQ. I notice twice the memory footprint - one for the JDBC result set and another copy for JOOQ. See pseudo code below. Is there any way to avoid this?
org.jooq.Query query = generateJOOQQuery(); String sql = query.getSQL(); // execute using standard JDBC java.sql.ResultSet result = execute(sql); // process result set using JOOQ org.jooqDSLContext context = DSL.using(...); org.jooq.Result<Record> jooqRecords = context.fetch(result); // this seems to make a copy of the JDBC result set // iterate through jooqRecords to process results Is there any way for org.jooq.Result to be used as just a wrapper over a java.sql.ResultSet without making copies? Thanks -- 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.
