Okay, so this isn't strictly server-side, but I'll post anyway..I am experimenting with Java for the first time - in particular with JDBC. I have managed to connect to my database using the code posted here And that works just fine.

Now I'm trying to create a class whose constructor will create a connection to the db, and then provide it with a query method to run a query and return a reault object.

I have a second programme which instantiates an object from this class def, passes a query string to it, receives the returned ResultSet and attempts to loop through it and print out the results.

My base class DBTalker is posted here . The 'calling' class, DBTest.java is shown here

Both classes compile without error, but I get the following exception at runtime:

Connected to brezhnev
Managed to create statement
Cound't get through the results:
java.lang.NullPointerException

Can anyone point out any obvious errors and/or bad practices please?

christo

The first thing that jumps out at me in DBTalker is the fact that the class defines a private var ResultSet result, and then the query method creates it's own ResultSet result. I'm betting that the result in the try of the query method is getting clobbered, because it's defined in the try, and the class's private result, which has, as of yet, not been assigned anything, is the object being returned.

I could be wrong, but that is the first thing I'd change.

TheLinuxDuck,

Thanks for your pointer - I hadn't noticed that I was re-declaring that ResultSet, so thanks very much. As it happens, I then got a new exception as shown below.

java.sql.SQLException: Operation not allowed after ResultSet closed

It turns out that this was because the ResultSet object gets destroyed when the statment, as suggested in the API docs "[close]...Releases this Statement object's database and JDBC resources immediately". However, the docs also state that "....A Statement object is automatically closed when it is garbage collected. When a Statement object is closed, its current ResultSet object, if one exists, is also closed", which all emplies that I don't need to bother with the stmt.close() method. whoopee


anyway, thanks


christo