Thanks for the report Richard, sorry it took me a while to find time to
debug.
> I’ve been using ecpg as part of my automated test framework to ensure
> my
> various SQL migrations have proper syntax. I believe I have run into
> an
> error where ECPG is reporting a syntax error that does not in fact
> exist.
I guess I agree, after all ecpg should accept everything that the
server accepts, right? :)
The problem is that ecpg expects every non-empty returning clause to
end with an "into <variable>" sectio to store the data in C. This
obviously does not make sense. I have to do more tests to see if making
the into clause optional breaks other things. If you have a large base
of test cases you're welcome to try it out too, once the patch is done.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
