2013/6/5 Roger Thomas <[email protected]> > > I think Jooq is for those who find that ORMs don't work for them. >> Those that find ORMs worth it don't need Jooq, they can use Hibernate or >> Mybatis or whatever ORM suits them best. >> Those that try to mix both usually find that they're running into >> problems with inconsistent data. The usual consequence of denormalized data >> if you will, or - from the Java perspective - of pointer aliasing. >> > > I very much agree (fit) this description of an end developer - I found > Jooq, having first tried to work with Apache > Empire-db<http://incubator.apache.org/empire-db/empiredb/empiredb.htm>as an > ORM alternative. Having first started to work with SQL based data > back in the late 80's I can see little advantage to trying to 'fit' such > data into an ORM model and when I have tried it's all gone rather wrong > rather quickly. Being SQL centric I'm far to aware of what can be done at > the data based level to gain performance to loss direct access to that > level. >
Back in the late 80's! Nice :-) So given your experience (and getting back to the original discussion), what is your take on strengthening support for JDBC's cursor update methods in ResultSet? -- 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.
