| From: | Anand Raman <araman(at)india-today(dot)com> |
|---|---|
| To: | Lista PostgreSql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: transaction aborted with error |
| Date: | 2001-03-22 15:30:47 |
| Message-ID: | 20010322210047.J7826@india-today.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I dont think so ..
Transactions need to be atomic.. Either succeed or fail.. I thik what
postgressql does is quite OK only a little irritating if u are issuing
command thru the psql terminal..
Anand
On Thu, Mar 22, 2001 at 10:15:54AM +0100, DaVinci wrote:
> Hello. I have a problem with Postgresql 7.1 beta (Debian packages).
>
> When I am in middle of transaction and there is an error, for example
> caused by trying to insert a tupla with a "not null" value without valor, I
> get error:
>
> NOTICE: current transaction is aborted, queries ignored until end of
> transaction block.
>
> I don't like this behaviour, is there any form of avoiding abortion of
> transaction on error?...
>
> Thanks.
>
> David
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
>subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>message can get through to the mailing list cleanly
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2001-03-22 15:31:07 | Re: Re: Call for platforms |
| Previous Message | Jonas Bengtsson | 2001-03-22 15:25:41 | Re: Re: OID as Primary Key |