By errorken
via koenserneels.blogspot.be
Published: Mar 05 2013 / 23:48
If you need to process large database result sets from Java you can opt for JDBC to give you the low level control required. On the other hand if you are already using an ORM in your application falling back to JDBC might imply some extra pain. You would be losing features such as optimistic locking, caching, automatic fetching when navigating the domain model and so forth. Fortunately most ORMs, like Hibernate, have some options to help you with that. While these techniques are not new, there are a couple of possibilities to choose from.
-
Google's next act: Diversify and conquer
-
FoundationDB Fault Tolerance Demo Video (& blog post)
-
Announcing the ability to Test Windows Phone 8 applications with Experitest SeeTest
-
Understanding the MvcRouteHandler and MvcHandler in ASP.NET MVC
-
SQL Server Compact Code Snippet of the Week #15 : flush data to disk immediately
-
21 Useful JavaScript Tips & Tricks with Demo
Comments
Lukas Eder replied ago:
This just shows that fetching 50k records is something extraordinary for a standard ("naive") Hibernate configuration...
Voters For This Link (12)
Voters Against This Link (0)