Re: Do SELECT statemetns create any locks on a 5.X OnLine Engine

In article <4hi2fn$2om@lynx.dac.neu.edu>, tgill@lynx.dac.neu.edu says... >I am writing an application that I don't want to interfere with other >applications accessing (doing update/inserts) the same database. Will >declaring a cursor with hold for a query select * from some_table create >any locks that the other processes might contend with? The database is >using logging if that matters. I am using ESQL/C against a 5.X OnLine >engine. It depends on the isolation level. You can get locking from a cursor like that with the repeatable read or cursor stability isolation levels. If you don't want it, you'll have to drop down to a less secure isolation level. An Ansi database is repeatable read by default, a non-Ansi database is committed read. -- William Harris william@carsinfo.com CARS Information Systems 4000 Executive Park Drive Cincinnati, OH (USA) 45241