How to structure code when connecting to databases

Question

I am developing a program in Java that I will use for registering data. I store the data in a MySQL database. We have not been making "big" programs in my class that uses databases for storage so what we have done is to make an adapter(We usually name it DBAdapter or something) that creates the connection and returns it. Then we have made a database handler class where all the statements are being executed. Then last the controller + view class have a reference to this handler and call whatever methods available.

However, my question is: When dealing with multiple tables and maybe different model data wouldn't it be good to separate the code in the handler into smaller chunks? Such as private classes or other public classes that a "main" handler could have references too? Example: If you make a system for a company that ship goods you probably would have a database that stores data about the goods. Then you would have a handler that has many select-statments for various stuff. You would also have many employees and then you probably want to separate the select-statements for the goods from the select-statements for the employees.

I also wonder if handler/adapter etc. is the correct terminology?

(This is not homework btw. I am making a program that will be a used for registering data for my iPhone app)

Thank you for your time.

Laurent Pireyn · Accepted Answer · 2011-04-25 19:18:50Z

1

You may want to look into Object-relational mapping libraries for Java, such as OpenJPA or Hibernate. If you'd rather stick to SQL - or like the fine-grained control - you may find Ibatis interesting.

In any case, I wouldn't manage the connections to the DB myself but rely on a connection pool, usually accessed through the DataSource interface.

answered Apr 25, 2011 at 19:18

Laurent Pireyn

6,8751 gold badge31 silver badges40 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

MJB · Accepted Answer · 2011-04-25 19:34:52Z

0

While ORM may well be where you head, I'd start with

a connection pool
implementing a DAO pattern strategy. If you are using Spring, look at JDBCTemplate - it will be pretty easy to convert this to HibernateTemplate, etc.

answered Apr 25, 2011 at 19:34

MJB

9,4196 gold badges37 silver badges49 bronze badges

Collectives™ on Stack Overflow

How to structure code when connecting to databases

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related