Re:

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "bts solutions" <bts_postgresql(at)hotmail(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re:
Date: 2003-03-04 15:22:25
Message-ID: 23161.1046791345@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

"bts solutions" <bts_postgresql(at)hotmail(dot)com> writes:
> We have implemented use of cursor in psql.

> + results =3D PQexec(pset.db, "begin work");
> + own_work =3D PQresultStatus(results) =3D=3D PGRES_COMMAND_OK;

I do not believe this works for the case where one is already inside a
transaction block. BEGIN will not report an error, so you'll end up
improperly issuing a COMMIT.

More generally, I'm not happy with having psql issue substantially
different SQL commands than what I gave it. I think it should be the
application's business to use a cursor, not psql's.

regards, tom lane

In response to

  • at 2003-03-04 08:31:40 from bts solutions

Browse pgsql-patches by date

  From Date Subject
Next Message Rod Taylor 2003-03-04 16:16:20 Re: [PATCHES] ALTER SEQUENCE
Previous Message bts solutions 2003-03-04 08:31:40