Nice analysis, all of you. My 2 cents is as follows: 1. If caring about performance on queries, use raw. 2. Evaluate if L2 is needed 3. Code maintainability
I think the most important thing to do is to evaluate the resulting sql while benchmarking your own app. JPA will not always produce the most effecient sql when it comes to N+1....or when it comes to handle large collections and lazyness... /hw -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/JPA-vs-DBUtils-tp4681918p4681934.html Sent from the TomEE Users mailing list archive at Nabble.com.
