On Thu, Aug 19, 2010 at 4:29 AM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > While testing the recent issue with unknown params in EXECUTE USING, I > accidentally did this: > > postgres=# DO $$ > DECLARE > t text; > BEGIN > EXECUTE 'SELECT ''foo'' || $1' USING 'bar' INTO t; > RAISE NOTICE '%', t; > END; > $$; > NOTICE: <NULL> > DO > > The mistake I made? I put the USING and INTO clauses in wrong order, INTO > needs to go first. We should throw an error on that, but it looks like the > INTO clause is just silently ignored.
Another option would be to make it work as expected. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
