Re: Informix vs. Oracle

I believe that Oracle only closes UPDATE cursors on a commit. Meaning that a normal cursor is created with hold by default and I know of no way to keep an update cursor open after a commit is done. I passed this infomation on to some in house Oracle consultants we have but they didn't think it was a serious problem. I disagree. If I have an update with a large number of rows in Informix I can enclose each fetch and corresponding update where current of in an individual transaction. In Oracle I must enclose the entire update cursor within a single transaction! In addition Oracle does not support the cursor stability isolation level! The solution I was given from the Oracle guys was to make sure that my update cursor does not contain a large number of rows. Gee thanks ;-((( -Bill } } ennis@ssax.com (Bill Ennis) wrote: } } :What about update cursors in Oracle? Oracle will lock EVERY row } :associated with an update cursor when the cursor is opened! Informix } :will lock the row when it fetches. In this case Infomrix is better } :for transaction independency. } } Such behaviour would have been a total showstopper for us. } Do you (or anyone else) know if Oracle have "hold" cursors (cursors } that are keept open accross a transaction)? } In case they do are all rows locked when the cursor is opened in this } case as well? } If that is the case what happen to these locks when a transaction is } committed? } } The Informix solution in this area is very good. } } } Nils.Myklebust@idg.no } NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway } My opinions are those of my company } The Informix FAQ is at http://www.iiug.org -- Bill Ennis Voice: 312-474-7516 SSA Fax: 312-474-7460 500 W. Madison email: ennis@ssax.com ennis@accesschicago.net