Hi Lukas, thanks for your suggestion but I prefere to use the jOOQ internal libarays and not the plain SQL. HikariCP is already implemented and working in general.
Am Freitag, 5. Oktober 2018 19:15:20 UTC+2 schrieb Lukas Eder: > > Hi Michael, > > I think you can totally safely ignore any concerns about garbage > collection when working with jOOQ. I mean: > > 1. Compared to the lag / latency of talking to a server that runs your SQL > statement with possibly tons of I/O, it seems negligible > 2. Benchmarks show that the most costly thing in jOOQ is the StringBuilder > that is used internally to create the dynamic SQL string. If you are *sure* > you need to optimise this (you probably don't), then extract the SQL > statement and bind variables from a jOOQ query using Query.getSQL() and run > the statement on JDBC directly. Again, YAGNI. > > Note: As you move on with the development of your application, you may > want to look into using a connection pool such as HikariCP. > > Hope this helps, > Lukas > > On Thu, Oct 4, 2018 at 6:03 PM Maverick Skywalker <[email protected] > <javascript:>> wrote: > >> Hi Lukas, >> >> thanks for your answers. >> >> *1)* Ok than I can use CRUD as primary method to handel my object or do >> have CRUD performance issues compared to the jOOQ SQL variant? (The >> question points primarly to Object Model and creating/destoying Objects >> inside of the Java garbage collector. >> >> *2)* I have fixed it. I have seeked at the wrong places Configuration >> and Settings Class. The Connection class would have been the right... >> >> Connection conn = DriverManager.getConnection(uRL, userName, password); >> conn.setAutoCommit(false); >> >> Am Donnerstag, 4. Oktober 2018 16:50:26 UTC+2 schrieb Lukas Eder: >>> >>> >>> On Thu, Oct 4, 2018 at 1:55 PM michael.may.2085 via jOOQ User Group < >>> [email protected]> wrote: >>> >>>> Hello Guys :) >>>> >>> >>> Hi Michael >>> >>> I'm new and still testing jOOQ how I can use it in the best way. >>>> >>> >>> Welcome! >>> >>> >>>> *1) *Is it intended that a CRUD insert also creates a select statement >>>> after the insert? (*MariaDB.log* - red marked line) I personally would >>>> say it's overhead especially because the update statement don't do that, >>>> but what do say the professionals? >>>> >>> >>> No, that's a known issue. I cannot seem to find the issue number on >>> Github, but it should definitely be fixed >>> >>> >>>> *2)* Is there any way to eliminate the "set autocommit" line? I want >>>> to disable auto commit at all but don't found any option. >>>> >>> >>> The jOOQ transaction API resets the autocommit flag after the >>> transaction to its previous value. That's what users would expect. After >>> all, you're in charge of your JDBC connection and its different flags, and >>> pass that to jOOQ, expecting it to be returned from jOOQ in the same state >>> as you passed it. >>> >>> So, you'll have to configure the autocommit flag to be false yourself. >>> >>> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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.
