RE: ONLINE 6.0 Locking

You don't need to commit the changes. When a database has logging off, every change is "committed" to the database as they happen. Technically, there is no committing of work to the database. It is just done, without possibility of rollback. So if an insert command should insert 10 rows into a table and it dies on the 6th row, there should be 5 rows in the table. The work cannot be rolled back or undone. Paul Watje watjep@hasting.com ---------- From: ilist To: informix-list Subject: ONLINE 6.0 Locking Date: Wednesday, June 14, 1995 6:15PM I have a database with logging turned off, because I'm making a lot of changes to it, and will turn logging on later. My problem is that I have declared a cursor that includes all the records in a table, and update particular ones in the process. What happens is the program eventually fails because the lock table overflows. Without "logging", how do I "commit" these updates every so often so this does not occur? -- ----------------------- J.E. "Rock" Solomon Jr. jesolom@PacBell.COM (510) 867-6615