From: | "Jose' Soares Da Silva" <sferac(at)proxy(dot)bazzanese(dot)com> |
---|---|
To: | "Meskes, Michael" <meskes(at)topsystem(dot)de> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org, pgsq-bugs(at)postgreSQL(dot)org, sferac(at)bo(dot)nettuno(dot)it |
Subject: | RE: [HACKERS] drop table inside transactions |
Date: | 1998-04-20 11:18:06 |
Message-ID: | Pine.LNX.3.96.980420111036.760A-100000@proxy.bazzanese.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 17 Apr 1998, Meskes, Michael wrote:
> Is this really a bug? I haven't seen any (commercial) system supporting
> this kind of transaction recovery. Once you drop a table the data is
> lost, no matter if you rollback or not.
>
SOLID does it, take a look:
SOLID SQL Editor (teletype) v.02.20.0007
(C) Copyright Solid Information Technology Ltd 1993-1997
Execute SQL statements terminated by a semicolon.
Exit by giving command: exit;
Connected to default server.
select * from cities;
CODE CITY
---- ----
SFO SAN FRANCISCO
STL ST. LOUIS
SJC SAN JOSE
3 rows fetched.
drop table cities;
Command completed succesfully, 0 rows affected.
drop table cities;
SOLID Table Error 13011: Table CITIES does not exist
rollback work;
Command completed succesfully, 0 rows affected.
select * from cities;
CODE CITY
---- ----
SFO SAN FRANCISCO
STL ST. LOUIS
SJC SAN JOSE
3 rows fetched.
Jose'
From | Date | Subject | |
---|---|---|---|
Next Message | Kapsaris | 1998-04-20 11:37:44 | v6.3.2 build on FreeBSD |
Previous Message | Jose' Soares Da Silva | 1998-04-20 10:08:45 | errors on transactions and locks ? |