From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
Cc: | Chris Schneider <cschneider(at)xede(dot)com>, <info(at)pgsql(dot)com>, <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Inquiry From Form [pgsql] |
Date: | 2003-07-03 16:12:46 |
Message-ID: | Pine.LNX.4.33.0307031012160.22238-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Thu, 3 Jul 2003, Bruno Wolff III wrote:
> On Wed, Jul 02, 2003 at 16:26:09 -0300,
> Chris Schneider <cschneider(at)xede(dot)com> wrote:
> > I know this is basic, but couldn\'t find and in a hurry to know the answer. When interfacing with PostgreSQL through PSQL, it appears that DML statements are auto-commited, that is, a change I make in one session is seen from another without the original session issueing a COMMIT. Is this a result of PSQL interface and if so, can it be turned off. Is PostgreSQL transactional in the sense that I can issue several DMLs and then ROLLBACK. If so, how. Thanks and sorry for the newbie question.
>
> Autocommit is the default mode for psql. Use "begin;" to start a transaction.
> And use "end;" to end a transaction. Note that unlike in sqlplus with Oracle,
> any errors while in the transaction will abort it and you have to start
> over.
>
> All DML and most DDL statements are rollbackable by 7.3. I believe in 7.4
> all DDL statements will be rollbackable.
Except drop database. That's one that'll probably never be rollbackable
;^)
From | Date | Subject | |
---|---|---|---|
Next Message | Evil Azrael | 2003-07-04 21:11:02 | INSERT ... SELECT problem in Mysql |
Previous Message | Rod Taylor | 2003-07-03 12:22:17 | Re: SEQUENCE and PRIMARY KEY |