Re: ONLINE 6.0 Locking

In article <3rn90h$6c0@gw.PacBell.COM>, jesolom@pbrock.srv.PacBell.COM (Rock Solomon) says: > >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? You could try getting an exclusive lock on the whole table at the start of your program - This would probably be the only way out and it would mean that nobody else can play with the table until you are finished.