Re: Cursors

I think the behaviour you describe happens only with scroll cursors , scroll cursors are used in inquiry with update options . There isn't a INFORMIX syntax which will solve your problem , however you may program your logic to return only the unique key form the query and use another cursor to read the record each time it is viewed. This would ensure that the info is up to date .... However you will not get the records which were inserted since your open your first cursor. Deepak Pant wrote in message <3489E0E6.7022@blr.sni.de>... >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