Hi, I've been doing Java development for a quite a while but haven't done it for a few years. Returning to it after this hiatus, I'm just overwhelmed with the amount of APIs and libraries, especially when it comes to managing DB connections, transactions, etc. There's Hibernate, Spring, BoneCP, HikariCP, and the list goes on. I know I'm mixing apples and oranges here a bit, but there are so many options to achieve essentially the same thing and most of them have poor or missing documentation, sloppy use-case demonstrations, and are grossly over-engineered IMO.
I'm glad I found JOOQ as it seems to help me get to where I want to be, plus it has great, clear documentation which helps a lot. I appreciate the fact that it allows the user the ability to manage DB access separately, however this is where I'm lost a bit. I want to write multi threaded server-side applications that query a DB (Postgres, for now). I want to be able to do things within transactions and sometimes outside of transactions. I (think I) need some kind of a connection pool manager because I'll have multiple threads (sometimes 100s) running at the same time. I have found HikariCP and I like the "looks" of it very much. Do I need something like Spring or Hibernate or any other framework for this or can I do without? (to manage transactions, for example) Basically I'd like to be able to quickly (read: with one line of code) get a connection (or DSLContext for Jooq), (optionally) begin a transaction, execute some SQL via Jooq, and (optionally) close the transaction. Any and all help is greatly appreciated! Thanks Lukas for creating and maintaining this wonderful library! -- 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.
