On Tue, Nov 08, 2005 at 11:03:50PM +0000, Ledina Hido wrote: > Quoting Tom Lane <tgl@xxxxxxxxxxxxx>: > > > 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 http://lnk.nu/postgresql.org/5sl.html -- Jim C. Nasby, Sr. Engineering Consultant jnasby@xxxxxxxxxxxxx Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
