Re: commit

Ingres does have transactions, but it in a way forces you to use auto commit(which means that you aren't using transactions). The concurrency model in Ingres (assuming it hasn't changed since I last used it) is brain dead. For example, if you insert a row into a table in Ingres with a primary key then most users will not be able to do anything with that table until you issue a commit! Why? Well Ingres is a page level locking database and so it locks all the pages that the primary key index traverses to add the row you are inserting. Which is usually about 95% of the table. Stupid I know, but that is how it works. Jim

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:tg2s64ms22fg57_at_beta-news.demon.nl...
>
> "J. G. Dutcher" <DutcherJG_at_navair.navy.mil> wrote in message
> news:DutcherJG-1505010753460001_at_clhrd7.chinalake.navy.mil...
> > I'm interest in moving my database to Oracle but am finding major
> > differences that make me wonder if it is worth the effort.
> >
> > In ingres (where my database currently resides) there is a "set
 autocommit
> > on" command that automatically commits each sql command. I've looked
> > through the Oracle sql server manual and can find no equivalent command.
> > Doesn't Oracle allow autocommit mode. Do I really have to code commit
> > after each sql statment?
> >
> > TIA for any help
> >
> > JG Dutcher (dutcherjg_at_navair.navy.mil)
>
> Apparently Ingres didn't implement the transaction concept ( a series of
> logical interdependent operations), which is just plain stupid.
> It would be very unadvisable to code a commit after each sql statement,
 that
> would be repeating this sin in Oracle.
>
> Regards,
>
> Sybrand Bakker, Oracle DBA
>
>
>
Received on Tue May 15 2001 - 19:03:01 CDT