Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nSgeR-0007hG-VJ for pgsql-docs@arkaria.postgresql.org; Fri, 11 Mar 2022 14:53:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nSgeP-0005vp-Ul for pgsql-docs@arkaria.postgresql.org; Fri, 11 Mar 2022 14:53:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nSgeP-0005vg-No for pgsql-docs@lists.postgresql.org; Fri, 11 Mar 2022 14:53:53 +0000 Received: from mail-oi1-x22f.google.com ([2607:f8b0:4864:20::22f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nSgeN-0006Nw-7c for pgsql-docs@lists.postgresql.org; Fri, 11 Mar 2022 14:53:53 +0000 Received: by mail-oi1-x22f.google.com with SMTP id ay7so9557618oib.8 for ; Fri, 11 Mar 2022 06:53:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=faO4i+BnKCj+rF40udwiM3flixsuhl2Vrt2JSTqFGlg=; b=LF/zj5qviDJSfit2QSINmPTNLl1V8SGO9an2nfEMRkIjIUl/s/agXc1oEJJv5M5Vut EW/gOSAJW0M9+E8feCvxZbTviBiajv4tOH472zcPmD8H7VIxa+eY074hB1/FzXgrSi5M iTyGlr9kFBfDY576PH5EVaZTbfbG15ZwQ93lLSMPqwU57ufaLxP2GkGiZSQP2hnzrydQ CstlzEy1Q63oVYqlvvtjlbRplhMjeU5ZOMcyfoqgLnWf3CRkJuIYJlS0Gw0EsqtW+Bzd 1/hP15Wkhj9J5rHUdTYAuFKVlEiYORXuoc35kzHw/3vCM/nhDrHkpi76VN35eeaFI8/p OXDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=faO4i+BnKCj+rF40udwiM3flixsuhl2Vrt2JSTqFGlg=; b=aXoK8LQo54oD2sdYjJ842JoVDvd0KU6YiOMRGmEN7qyQC+4CWA55zuZZsq32FoqJoV NJWTIGEDvgovvjxputd5est1G62OJ+t9FLtvqPB+PmM9w3fePaJWFvgwHAiaG9vrW4qT DFg6a87lfiYwmDtRLzkeoc/m/pkmzLzc+iNu2TAYnz+eFVPNU+6N0fexcUwMCaWJbrWz d/k0YkX7oPyT/DL7qK4Kj0c62CRyh1zS+tKotbiuk8rZcR8vq9aOHoPx1HH6wx8XN7Qq vUBOavz+qf684YchrrlmgEDSsuTr7zQqZRnRvFy1JFzeYyP8Ef0vy1Xzm52N4ur2ZQR7 3F9A== X-Gm-Message-State: AOAM5311PQ/Qxdv4kL1JFRKq6P7v9xZqz+XcL6qB956i7NzFbF82B11c 7UZK/5wspM59bieE+ONha77BZTzQgLVwV9I1v+s= X-Google-Smtp-Source: ABdhPJxyxrq0laTadZKV0ukbGPSJWOZZ/ucd9qDIhFPr5+Whc+vl3XKwhjsuyap9p/hSazocTLiw92KmERmy/TZQ/kA= X-Received: by 2002:aca:58d7:0:b0:2ec:a246:ad04 with SMTP id m206-20020aca58d7000000b002eca246ad04mr847551oib.53.1647010429259; Fri, 11 Mar 2022 06:53:49 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a9d:1ab:0:b0:5b2:1f3e:20e8 with HTTP; Fri, 11 Mar 2022 06:53:48 -0800 (PST) In-Reply-To: <164698257526.655.5597762736617707697@wrigleys.postgresql.org> References: <164698257526.655.5597762736617707697@wrigleys.postgresql.org> From: "David G. Johnston" Date: Fri, 11 Mar 2022 07:53:48 -0700 Message-ID: Subject: Re: returning clause is not clearly documented To: "mf.esp1400@gmail.com" , "pgsql-docs@lists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000093d46305d9f27f92" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000093d46305d9f27f92 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Friday, March 11, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/dml-returning.html > Description: > > Hello there > I'm not good enough in english, so have my excuse. > > I don't undestand how Returning clause work when more than on row are > affected. i.e I have an update with 3 rows affected and I want to have th= en > to return to then front-end. > How I must do in same cases? > It doesn=E2=80=99t matter how many rows are affected, returning will return= them all. David J. --00000000000093d46305d9f27f92 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Friday, March 11, 2022, PG Doc comments form <noreply@postgresql.org> wrote:
The following documentation comment has been logged on the = website:

Page: https://www.postgresql.org/docs/14/dml-returning.html
Description:

Hello there
I'm not good enough in english, so have my excuse.

I don't undestand how Returning clause work when more than on row are affected. i.e I have an update with 3 rows affected and I want to have then=
to return to then front-end.
How I must do in same cases?



--00000000000093d46305d9f27f92--