Re: Cursors

Hi Deepak, Is your database logging? If so look into isolation levels. If you set an isolation level of cursor stability or repeatable read you will place a shared lock as you fetch each record from the cursor. With cursor stability the lock is released when you fetch the next row from the cursor (unless you update it); with repeatable read the lock is released at the end of the current transaction. -Bill } Hello, } } I have a query regarding the informix cursors. The usual behaviour } on the opening of the cursor is that a number of records which match } the where clause in the open cursor statement are fetched. A fetch } from the cursor fetches the records from the local cache and not } from the server. In my application this is causing a problem since } other informix sessions may be updating the table as well and hence } the values which are provided by the cursor may be invalid. } } Now is it possible that whenever I issue a fetch cursor the records } are fetched from the server/database itself and not the cursor which } probably has gone stale. } } Regards } Deepak } -- Bill Ennis Voice: 312-474-7516 SSA Fax: 312-474-7460 500 W. Madison email: ennis@ssax.com ennis@accesschicago.net