Home/ Questions/Q 686923
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T02:04:27+00:00

I’m using a Java wrapper for SQLite called SQLiteJDBC – this may have some

  • 0

I’m using a Java wrapper for SQLite called SQLiteJDBC – this may have some bearing on any answers…

I have a table which I’ve displayed in a GUI, within that UI I have a button for the fields for an individual row of that table. When I save my changes I do this…

Statement stmt = connection.createStatement();
stmt.execute("update 'tableName' set 'fieldName'=1 where userid=1");

int updateCount = stmt.getUpdateCount();

My connection is valid, I get no exceptions thrown and getUpdateCount() returns ‘1’ indicating that one row has been updated. However my table is not updated. I’ve spent the last few hours trying to work out what’s going on but I’m not having any luck. Help!!

UPDATE

The problem seems to be that it’s not committing the changes I make. While the application is running my changes are visible but as soon as I close the application and reopen it or check the database directly my changes are lost and we’re back to square one. What’s going on??!

Auto-commit is set to true and if I set it to false and try to commit I get an exception thrown.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    My problem was that I was relying on the garbage collector to clear up my used ResultSets, I was not explicitly closing them.

    In SQLite accessing a table locks the entire database so these used ResultSets that were still ‘open’ were preventing my obtaining write access to a table after I’d read its contents.

    If you have this problem and are using SQLite just call close() on each ResultSet when you’re done with it. (You may also want to try doing the same to any PreparedStatements, I’d assume that these would also close any ResultSets they were used to create but I haven’t experimented to verify this.)

    • 0