This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
1. In a given transaction, if I need to insert/update few records (say around 5 records) in different tables (say around 5 tables), can someone tell me which is the best approach to follow: JDBC batch updates or stored procedures?
2. We are going to use Hibernate3.0 in our project. In that case which is the prefered solution: Using JDBC batch updates through Hibernate or using stored procedures through Hibernate?
for 5 records for 5 tables, executing sql statements should be no problem.
if you are writing some financial application that needs to do this thousands of times per minutes then stored procs are always the fastest means of executing crud to the database.
if milliseconds don't mean much to you, then hibernate will make your code much more manageable going forward with changes and extensions to your codebase since then you have the means to create model objects and map your database tables in hbm.xml files and simple write code thats as simple as.. er um.. hey lets even use Spring as a framework! ::
hibernate is pretty well designed so that it doesn't add much overhead versus using raw JDBC. the only reason to not use hibernate would be if you truely need the speed of stored procs, or your database is so old and legacy with no good indexing or ids, hibernate becomes a pain to do true mappings. hibernate simply loves good data models.
Joined: Dec 27, 2005
Thanks for the details. We have planned to use Spring also.