Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

On Mon, Oct 2, 2017 at 12:44 PM, Tom Lane wrote: >> And I'm saying - that argument is bogus. Regardless of what people >> want or what we have historically done in the case where the >> record/row is the only INTO target, when there are multiple targets it >> seems clear that they want to match u

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

2017-10-02 18:44 GMT+02:00 Tom Lane : > Robert Haas writes: > > On Mon, Oct 2, 2017 at 12:28 PM, Tom Lane wrote: > >> I'm not sure if that's true or not. I am sure, though, that since > >> we've done B for twenty years we can't just summarily change to A. > > > I agree, but so what? You said t

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

Robert Haas writes: > On Mon, Oct 2, 2017 at 12:28 PM, Tom Lane wrote: >> I'm not sure if that's true or not. I am sure, though, that since >> we've done B for twenty years we can't just summarily change to A. > I agree, but so what? You said that we couldn't adopt Pavel's > proposal for this

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

On Mon, Oct 2, 2017 at 12:28 PM, Tom Lane wrote: > Robert Haas writes: >> On Tue, Sep 19, 2017 at 3:18 PM, Tom Lane wrote: >>> That's certainly a case that we ought to support somehow. The problem is >>> staying reasonably consistent with the two-decades-old precedent of the >>> existing behavi

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

Robert Haas writes: > On Tue, Sep 19, 2017 at 3:18 PM, Tom Lane wrote: >> That's certainly a case that we ought to support somehow. The problem is >> staying reasonably consistent with the two-decades-old precedent of the >> existing behavior for one target variable. > My point is that you obje

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

On Tue, Sep 19, 2017 at 3:18 PM, Tom Lane wrote: > Robert Haas writes: >> I think the fact that single-target INTO lists and multiple-target >> INTO lists are handled completely differently is extremely poor >> language design. It would have been far better, as you suggested >> downthread, to ha

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

> On 20 Sep 2017, at 01:05, David G. Johnston > wrote: > > On Tue, Sep 19, 2017 at 11:29 AM, Tom Lane > wrote: > ​T​hat​ ​doesn't work today, and this patch doesn't fix it, but it does create > enough confusion that we never would be able to fix it. > > I'd be much h

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

Robert Haas writes: > I think the fact that single-target INTO lists and multiple-target > INTO lists are handled completely differently is extremely poor > language design. It would have been far better, as you suggested > downthread, to have added some syntax up front to let people select > the

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

"David G. Johnston" writes: > On Tuesday, September 19, 2017, Tom Lane wrote: >> I'd be much happier if there were some notational difference >> between I-want-the-composite-variable-to-absorb-a-composite-column >> and I-want-the-composite-variable-to-absorb-N-scalar-columns. > If we change to c

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

On Tuesday, September 19, 2017, Tom Lane wrote: > Pavel Stehule > writes: > > 2017-09-14 12:33 GMT+02:00 Anthony Bykov >: > >> As far as I understand, this patch adds functionality (correct me if I'm > >> wrong) for users. Shouldn't there be any changes in doc/src/sgml/ with > the > >> descripti

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

On Sat, May 13, 2017 at 4:20 PM, Tom Lane wrote: > IIRC, the reason for disallowing that is that it's totally unclear what > the semantics ought to be. Is that variable a single target (demanding > a compatible composite-valued column from the source query), or does it > eat one source column per

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

2017-05-14 5:04 GMT+02:00 Pavel Stehule : > > > 2017-05-13 22:20 GMT+02:00 Tom Lane : > >> Pavel Stehule writes: >> > I am working on migration large Oracle application to Postgres. When I >> > started migration procedures with OUT parameters I found following limit >> >> > "record or row variabl

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

2017-05-13 22:20 GMT+02:00 Tom Lane : > Pavel Stehule writes: > > I am working on migration large Oracle application to Postgres. When I > > started migration procedures with OUT parameters I found following limit > > > "record or row variable cannot be part of multiple-item INTO list" > > IIRC,

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

Pavel Stehule writes: > I am working on migration large Oracle application to Postgres. When I > started migration procedures with OUT parameters I found following limit > "record or row variable cannot be part of multiple-item INTO list" IIRC, the reason for disallowing that is that it's totall

[HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

Hi I am working on migration large Oracle application to Postgres. When I started migration procedures with OUT parameters I found following limit "record or row variable cannot be part of multiple-item INTO list" I checked code and it looks so this limit is not necessary for ROW types (what is