Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


advertisement
 

Tip: Disabling AutoCommit in JDBC

Learn why it is unwise to commit after every insert.


advertisement

WEBINAR: On-Demand

Unleash Your DevOps Strategy by Synchronizing Application and Database Changes REGISTER >

Only once the development part of the project is complete do we tend to look at the performance of our application's interaction with the database and realize that the transactions are relatively slow. A potential source for bottleneck could be the autoCommit feature of your connection to the database.

Most of the time, database operations are time-consuming when compared to in-memory operations. In addition, such actions add to the overhead. Ideally, instead of auto committing after every insert, it is ideal to commit once the transaction is complete.

For example, instead of committing every insert, while you are reading from a file and inserting records, it is better to commit after the entire file is read and the database updated. There are numerous other cases where you can consider this options.

//Connect to the database 
Connection connection = DriverManager.getConnection( host, username, password );
    
connection.setAutoCommit (false); // Setting the auto commit to false. This will ensure that commit is not automatic

//You can enable it by passing true subsequently when you think it is appropriate.

 

Visit the DevX Tip Bank

 





   
Sridhar M S. is a Java developer from Bangalore, India. He holds a master's degree in Computer Science.
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date