From: | Matthias Raffelsieper <hoschiraffel(at)freenet(dot)de> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #10836: Rule with RETURNING claims incorrect type |
Date: | 2014-07-02 14:06:27 |
Message-ID: | 53B411E3.6070100@freenet.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 7/2/14 3:51 PM, Marko Tiikkaja wrote:
> On 7/2/14 3:05 PM, hoschiraffel(at)freenet(dot)de wrote:
>> [...]
>
> You're actually only returning a single column. RETURNING (id, info) is
> the same as RETURNING ROW(id, info), which is very different from
> RETURNING id, info. See
> http://www.postgresql.org/docs/9.3/static/rowtypes.html, for example.
>
> Note that this behaviour is the same as in SELECT lists; SELECT (id,
> info) FROM foobar; will also only give you a single column.
Hello Marko.
Thanks for the explanation and sorry for not spotting my mistake. Please
close this bug as invalid.
It would however have helped if I had gotten back the expected type and
the actually provided type; even in verbose mode this was not supplied.
Would this be possible, or is there already a configuration option to
enable this?
Cheers,
Matt
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-07-02 15:38:51 | Re: BUG #10675: alter database set tablespace and unlogged table |
Previous Message | Tom Lane | 2014-07-02 13:53:37 | Re: BUG #10836: Rule with RETURNING claims incorrect type |