| From: | Ledina Hido <lh1101(at)ecs(dot)soton(dot)ac(dot)uk> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Transactions, Triggers and Error Messages |
| Date: | 2005-11-09 00:45:37 |
| Message-ID: | BEC2C039-9149-4027-9AA0-5FC7FDAE72C7@ecs.soton.ac.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
That's great. Thank you very much for you help.
Ledina
On Tue, Nov 08, 2005 at 11:03:50PM +0000, Ledina Hido wrote:
> Quoting Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> > What are you running this in? ISTM this is a problem with bad
> structure
> > of client-side code, not something to be fixed on the server side.
> >
> > regards, tom lane
>
>
> I'm using pgAdmin3. Basically when I run the query the first time it
> gives the correct error but if I re-run it, then it says "ERROR:
> current transaction is aborted, commands ignored until end of
> transaction block". Should I be doing something else, ie should I be
> explicitly rolling back once the exception is raised so I don't get
Yes.
> this error? And if so how can I "catch" the exception. Sorry for my
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Will Wright | 2005-11-09 00:47:44 | Re: Programmatic method to determine currently installed Windows PostrgreSQL version |
| Previous Message | Jim C. Nasby | 2005-11-09 00:32:45 | Re: Transactions, Triggers and Error Messages |