I sort of stumbled on this thread a little late but is the issue that you (digulla) can't assert the SQL that is generated by jOOQ?
It sounds like what your looking for an abstraction above JDBC to mock. I did this for my library: https://github.com/agentgt/jirm/tree/master/jirm-core/src/main/java/co/jirm/core/execute However I think the spirit of jOOQ is to embrace JDBC so JDBC is exposed much more all over. Thus I think Lukas's Mocking JDBC contributions should be a good starting point. Of course I think your insane for mocking JDBC when you can just execute to a real database... but I too used to drink the mocking cool-aid :) -Adam On Monday, February 18, 2013 7:51:07 AM UTC-5, digulla wrote: > > On Monday, February 18, 2013 11:52:43 AM UTC+1, Lukas Eder wrote: > > > Not right now. I'll first see how this is adopted. Feel free to >> > suggest / contribute one >> >> Note that I'm going to implement a file-based API soon, as I think >> that is easier to handle for end users: >> https://github.com/jOOQ/jOOQ/issues/2208 >> >> A draft implementation is already included in 3.0-RC1 >> > > How about a parser that can read the output of Record.toString()? That > would make it dead simple to produce the test data (just run the query once > against a real database). > > Regards, > > A. Digulla > -- 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/groups/opt_out.
