| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Vitaly Belman <vitalyb(at)gmail(dot)com> |
| Cc: | pgadmin-support(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Fwd: [NOVICE] Autocommit in Postgresql |
| Date: | 2005-05-12 15:25:01 |
| Message-ID: | 4283754D.7020804@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-novice |
Vitaly Belman wrote:
>
>>That's the problem... Is there a way to make it implicitly open a
>>transaction? For example now in pgAdmin when I play with SQLs I have
>>to do begin and rollback constant because whenever a query fails it
>>refuses to do anything at all until I "rollback", and then of course I
>>have to do "begin" again unless I want my queries to be real.
Apparently I don't really understand the problem. If you don't
explicitely open a transaction, everything you execute within one
execute command will be processed within one transaction by the backend.
If you want to execute step by step, just mark the commands and hit F5.
> (I am not sure if any of them read this list).
At least I am not on the list, so please continue crossposting if
applicable.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vitaly Belman | 2005-05-14 11:02:17 | Re: Fwd: [NOVICE] Autocommit in Postgresql |
| Previous Message | Vitaly Belman | 2005-05-12 14:46:35 | Fwd: [NOVICE] Autocommit in Postgresql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keith Worthington | 2005-05-12 17:48:02 | syncing a serial across tables |
| Previous Message | Scott Marlowe | 2005-05-12 15:14:38 | Re: Using PgSQL in high volume and throughput problem |