| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Chris Schneider <cschneider(at)xede(dot)com> |
| Cc: | info(at)pgsql(dot)com, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Inquiry From Form [pgsql] |
| Date: | 2003-07-03 11:19:17 |
| Message-ID: | 20030703111917.GA19441@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2003-07-03 12:22:17 | Re: SEQUENCE and PRIMARY KEY |
| Previous Message | g.o.d | 2003-07-02 11:32:56 | Weird order problem (ignoring whitespaces?) |