From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Benedict Holland <benedict(dot)m(dot)holland(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: insert select fails inside of function |
Date: | 2012-06-22 19:44:15 |
Message-ID: | 17596.1340394255@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Benedict Holland <benedict(dot)m(dot)holland(at)gmail(dot)com> writes:
> I am scratching my head over this one. I have a basic function which
> populates a table inside of it (declared outside of the function but that
> shouldn't matter) and it requires something like
> insert into table1 (col1, ...)
> select * from foo
> and I get the error "query has no destination for result data". This is
> surely not the case as it's going directly into the insert statement which
> doesn't have output. Any idea how to get around this particularly annoying
> problem?
What PG version? Could we see the exact text of the function? I'm
wondering about aliasing problems stemming from function variables named
similarly to the target table or its columns --- newer PG versions are
brighter about that sort of conflict than older ones.
> I have to say, making the switch from t-sql to postgresql has been
> fairly easy except for function debugging.
RAISE NOTICE is the usual substitute for what I think you were doing on
t-sql. Also, I think EDB is still supporting their plpgsql debugger, so
you might consider experimenting with that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Benedict Holland | 2012-06-22 20:11:10 | Re: insert select fails inside of function |
Previous Message | Виктор Егоров | 2012-06-22 19:18:49 | Re: Extensions and roles for access administration |