Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!cs.utexas.edu!uunet!pmafire!mica.inel.gov!gem-hy!cdm
From: cdm@gem-hy.Berkeley.EDU (Dale Cook)
Newsgroups: comp.databases
Subject: Re: Rollback in ORACLE
Message-ID: <1991Jan10.234950.19957@inel.gov>
Date: 10 Jan 91 23:49:50 GMT
References: <1991Jan10.160300.8839@cs.umn.edu>
Sender: news@inel.gov
Reply-To: cdm@gem-hy.Berkeley.EDU (Dale Cook)
Organization: Idaho National Engineering Laboratory, Idaho Falls, Idaho
Lines: 44

In article <1991Jan10.160300.8839@cs.umn.edu>, peng@cs.umn.edu (Lim Ee
Peng) writes:
|> 
|> I used Oracle Sqlplus recently and found out that the rollback command
|> doesn't affect 'create table' operation at all.  All the while, I thought
|> that 'create table' is simply an update to the system tables and rollback
|> should also work.
|> 
|> I attached a script below to demonstrate my point.
|> Can someone who knows Oracle well explain to me why does the rollback
|> work this way?
|>
|>  [Example deleted...]

It's not the ROLLBACK that's not working the way you think it should, it's
the CREATE command.  If you look up COMMIT in the SQL*PLUS command ref.,
it gives the list of commands that issue a COMMIT as part of their processing.
CREATE is one of them.  So are most other commands that alter the actual
database structure (not just modify the data).  Once a COMMIT is issued,
of course, ROLLBACK has no effect on everything up to the COMMIT.

Why? I suspect it has to do with internal issues within Oracle, probably
to simplify an extremely complex circumstance.

|> Thanks.
|> 

Welcome.


---Dale Cook     cdm@inel.gov

========== long legal disclaimer follows, press n to skip ===========
^L
Neither the United States Government or the Idaho National Engineering
Laboratory or any of their employees, makes any warranty, whatsoever,
implied, or assumes any legal liability or responsibility regarding any
information, disclosed, or represents that its use would not infringe
privately owned rights.  No specific reference constitutes or implies
endorsement, recommendation, or favoring by the United States
Government or the Idaho National Engineering Laboratory.  The views and
opinions expressed herein do not necessarily reflect those of the
United States Government or the Idaho National Engineering Laboratory,
and shall not be used for advertising or product endorsement purposes.