Mark Hiles wrote:
bradm6406 <[EMAIL PROTECTED]> writes:
Any chance that you are not committing your transactions? Changed data
would appear to be there while you're connected to the database but
disconnecting (without a commit) and then re-connecting it would appear as
though your database was overridden, when really the data was never saved.
Brad
Thanks, my problem is now solved. I was forgetting to commit my data before
disconnecting from the db.
Unfortunately, I have a new issue. I've been using the next() method to run
through a ResultSet. But a lot of the other methods I try using, I receive an
error stating that I'm not using a scrolling cursor.
For example, I don't see why I can use next() but not previous().. I'm trying to
count the number of results from a specific query..
Hi,
You might find this link helpful
http://db.apache.org/derby/docs/dev/devguide/rdevconceptssur.html
"A scrollable updatable result set maintains a cursor which can both
scroll and update rows."
Narayanan
