Re: Strange transactional problem with my Oracle database?

>From: "Jim Kennedy" kennedy-family_at_attbi.com
>Date: 2002-08-23 23:17 Eastern Daylight Time
>

>Sql Server and Oracle are different databases. Sql Server assumes you want
>to "auto commit" Since ADO is a MS concept and really more designed with
>SQL Server in mind it does auto commit. (There is probably a setting to NOT
>autocommit, but the default is to auto commit.)
>
>In SQL Server locks and transactions are bad things that prevent other
>people from doing the simplest of things. In Oracle this is not the case
>and things work as a database with ACID properties should. So in SQL Server
>it can be ACID, but you have to make sure you do things in very explicit
>ways to make it so. In Oracle it assumes you want to do it right.

What is the SQLPlus Worksheet referred to earlier? I am using the scott / tiger practice version from Oracle. In that, if you exit SQLPlus by entering the command "EXIT," even without having specifically done a COMMIT, then all changes are saved. If you exit by alt-F4 or x-ing the window, then all changes (assuming no definitions were done) are discarded.

Ross
Roebuck, South Carolina
http://community.webshots.com/user/ross_klatte Received on Mon Aug 26 2002 - 08:20:15 CDT