Re: CommitFest 2009-09, two weeks on
Michael Meskes <meskes@postgresql.org>
From: Michael Meskes <meskes@postgresql.org>
To: Boszormenyi Zoltan <zb@cybertec.at>
Cc: Michael Meskes <meskes@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org, Hans-Juergen Schoenig <hs@cybertec.at>, Dan Colish <dan@unencrypted.org>
Date: 2009-10-02T13:37:58Z
Lists: pgsql-hackers
On Thu, Oct 01, 2009 at 09:05:55PM +0200, Boszormenyi Zoltan wrote: > Yes, but technical problems and solutions do. ECPG claims > to be ESQL/C compatible, but at places it's only half compatible. Where does it claim to be fully compatible? > This comment is misleading and reflects quite a narrow POV. > Not only OPEN and DECLARE may be out of scope, > but FETCH and CLOSE as well. The reason why ESQL/C > allows this construct is that this ultimately allows using > embedded SQL in event-driven code in a straightforward way. > For this purpose, native ECPG code is not usable currently, > or you need programming tricks, like tracking whether the > cursor is open and protecting DECLARE and OPEN under > some conditional branch to avoid double open, etc. A straight > DECLARE, OPEN, FETCH(s) and CLOSE series in > the same function is only good for batch programming. Examples? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: meskes@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!