Best practice needed to use PraparedStatments

Question

Dear Experts;
I am using plain JDBC to intract with database, it works fine but what I am doing is, creating Connection and PreparedStatement in every method (where I need db interaction) and closing connection, resultSet and preparedStatment instances.
What I required, I dont need to create/close connections myslef. Yes If I want to insert a row in db i can achieve this by ... (but below I am using Statment not preparedStatmenmt, what will be the case in preparedStatement?)
public static boolean insert (string query)
// creating Connection
// creating statment
// executing stament.executeQuery(query)
// if insert successful setting retuenValue = true
// closing connection and statment
public insetRecord (User user)
  if (insert ("insert into user valaues "+user.getUserId+","+user.getUserId+")"))
  else
}any practice that you are using with preparedStatment.
I want to make this inset method generic for every table (and I want to use preparedStatments) and similarly fetching methods too.
thanks in advance
- Tahir

Answer 1

I am using plain JDBC to intract with database, it
works fine but what I am doing is, creating
Connection and PreparedStatement in
every method (where I need db interaction) and
closing connection, resultSet and
preparedStatment instances.Refractor to utility classes and methods. Or consider 3rd party DAO/ORM stuff, like Hibernate. They will care about them then.
What I required, I dont need to create/close
connections myslef. Yes If I want to insert a row in
db i can achieve this by ... (but below I am using
Statment not preparedStatmenmt, what will be the case
in preparedStatement?)Not closing them is bad practice. Consider connection pooling and reuseable SQL query strings for PreparedStatement.
I want to make this inset method generic for
every table (and I want to use preparedStatments) and
similarly fetching methods too.One word again: Refractor.
If your application is getting bigger, then it is really worth to take a look for a solid ORM solution. Hibernate is great.