From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Cc: | max1(at)inbox(dot)ru, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: "there is no way to insert less than one row" |
Date: | 2021-03-24 23:18:50 |
Message-ID: | CAKFQuwY4edByxicpaFX5vc=meE=PM7ivZzvuiqhuzo_YZft0iQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, Mar 24, 2021 at 1:29 PM Peter Eisentraut <
peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> On 20.03.21 20:16, PG Doc comments form wrote:
> > So, the last insert command inserted zero rows. What is meant by "there
> is
> > no way to insert less than one row"?
>
> I think the point was that you can't insert partial rows.
>
Sure, if you think its related to the following sentence. If you think its
related to the subsequent one it means "cannot insert zero rows". Frankly,
both interpretations are wrong, inserting an explicit column list with
omitted columns populated using defaults is a "partial row API" for
inserting data.
I'm also not fond of the word "conceptually" here - its actually a physical
reality that regardless of how one or more rows are supplied they are
inserted one-at-a-time so far as constraints, discussed in the previous
chapter, are concerned (though some constraints can be deferred).
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2021-03-24 23:19:36 | TLS acronym |
Previous Message | Daniel Gustafsson | 2021-03-24 20:57:02 | Re: Update to reflect that TLS1 and TLSv1.1 are now deprecated |