Realising changes in an open ResultSet

Question

Hello,
I'm currently working on a project using simple JDBC and Swing and having some problems getting the application to realise changes made to a resultset that is open all the time.
I have a simple Manager class that, in essence, looks like this:
class CustomerManager {
private ResultSet results;
private int count;
public void load() {
   Statement st = con.createStatement();
   results = st.executeQuery( "select * from customers" );
   results.last();
   count = results.getRow();
public void getCount() {
   return count;
public Customer getCustomer( int index ) {
   results.absolute( index+1);
   //Load via JDBC DAO
   return new JDBCCustomer( results );
}There are several thousand customers in my database so I guess this is the preferred way of doing it (Correct?)
To update a customer, the code looks somewhat like this:
public void updateCustomer( int id, Customer cust ) {
   String sql = "update customers set name = .... where id=" + id );
   Statement st = con.createStatement(  sql );
   st.executeUpdate()
}The problem is that because the update takes place outside the already open ResultSet it doesn't seem to realise the changes to a specific customer. The only solution I've found is to reload the entire ResultSet by calling CustomerManager.load() once again, this is not desirable because there are several different ways of loading the resultset and I don't want to keep track of which way I did it. Is there an easier way of doing things? a reload() method perhaps or maybe a constant telling the resultset to be aware of changes?
I am using MySQL 5.0 with the MySQL 3.1.13 JDBC Driver.
Thanks in advance!
//John

Answer 1

>
Really? Care to elaborate? I thought it was the only
way of doing things when you had really big
resultsets. What would you do/recommend?In terms of memory/process several thousand isn't very large. I have a transaction based server that is designed to cache 2 million entities. I certainly don't use an open result set for that.
In terms of a GUI having any sort of display with several thousand rows is wrong. Users know what they are looking for so make them give you that information and then return the couple or even one record that they are actually looking for.