This is a very small DB Connector code in Java as a wrapper class to Apache DBUtils.
The Commons DbUtils library is a small set of classes designed to make working with JDBC easier. JDBC resource cleanup code is mundane, error prone work so these classes abstract out all of the cleanup tasks from your code leaving you with what you really wanted to do with JDBC in the first place: query and update data.
Some of the advantages of using DbUtils are:
- No possibility for resource leaks. Correct JDBC coding isn’t difficult but it is time-consuming and tedious. This often leads to connection leaks that may be difficult to track down.
- Cleaner, clearer persistence code. The amount of code needed to persist data in a database is drastically reduced. The remaining code clearly expresses your intention without being cluttered with resource cleanup.
- Automatically populate Java Bean properties from Result Sets. You don’t need to manually copy column values into bean instances by calling setter methods. Each row of the Result Set can be represented by one fully populated bean instance.
DbUtils is designed to be:
- Small – you should be able to understand the whole package in a short amount of time.
- Transparent – DbUtils doesn’t do any magic behind the scenes. You give it a query, it executes it and cleans up for you.
- Fast – You don’t need to create a million temporary objects to work with DbUtils.
DbUtils is not:
- An Object/Relational bridge – there are plenty of good O/R tools already. DbUtils is for developers looking to use JDBC without all the mundane pieces.
- A Data Access Object (DAO) framework – DbUtils can be used to build a DAO framework though.
- An object oriented abstraction of general database objects like a Table, Column, or Primary Key.
- A heavyweight framework of any kind – the goal here is to be a straightforward and easy to use JDBC helper library.