Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJdYJ-005zUC-0S for pgsql-general@arkaria.postgresql.org; Tue, 18 Jun 2024 18:27:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sJdYF-000VFj-Oy for pgsql-general@arkaria.postgresql.org; Tue, 18 Jun 2024 18:27:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJdYF-000VFW-AW for pgsql-general@lists.postgresql.org; Tue, 18 Jun 2024 18:27:28 +0000 Received: from mail-oa1-x36.google.com ([2001:4860:4864:20::36]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sJdYC-002KJI-H2 for pgsql-general@lists.postgresql.org; Tue, 18 Jun 2024 18:27:26 +0000 Received: by mail-oa1-x36.google.com with SMTP id 586e51a60fabf-2549c883c43so35668fac.1 for ; Tue, 18 Jun 2024 11:27:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718735242; x=1719340042; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=LOhM1AZjNw6yoEY57cB8RIFQ1Z98t99v6QvqcgWuDjw=; b=DQ7YG5hj/v1VaxGI2NOAKM2fUXbDUriZ5KGA4p6s6359h2adh4lhyQZvBiAqC0Qig8 ih0KIpmyDhhpe3AWbCrtIq7ezmPJZgx+ecwinhO3ovHAMxB64QPJOi+FoFWIbLvBud4s K2cpvU8rrtaormEM7JjR2Q9wf3ufiYH9WCQwcZuQrx8q0uKtBLOfX38lzli8bjdM/MUx n011xa/mgOhZ8Eq7rr6Yb4hfqhrAIEikUi7QbtQhuOjGhI89oHiz/9dMaa+q+z0P12Uu oSN3uV5/lsvs9yKnoN93V49RlWZxfRGFvp07vaiiDYjSb4SGfKgYjOn/Utp8Z3RYP8cK 5NRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718735242; x=1719340042; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=LOhM1AZjNw6yoEY57cB8RIFQ1Z98t99v6QvqcgWuDjw=; b=Kra2G9GnDp6ZggwbWp7NA53m/g5TYLQNy+MN6GUhBI9plIylfAq0hsgrTCDWHDs7KA x37Cmh/mwwe1tElxXV54laIHbEAV8ElvOMKCEosVkUEcwsZmyzxb1YU2Gdhr2WIkJGyK WDvdMiplnLWHGEzKxUqKsnFeo9IiIcBilXaYPI6xvOHVGQdT63qqHf9h9/3uF1p+z/Vt RV7CV74BB1GKOsXh2rsE0w2zBZqCqqT1r1mphjrO26ZvDvpE4nMu6f2+zV3K8Kgr0gWj R3vUGoeCKYi60/RcSAlkc/qs0dG+8uYdfARl0cJ9gePk54PA2RvszRdvbSQv04Cfuse7 aEvw== X-Gm-Message-State: AOJu0YxQQ/YKiZnpxyemAqgHAXB1og6qlopWrHfiaoDjMqxjmTNGrnfi 9FgXz6lFhEEKEP7XVVBhdPvz0SEZx/1NP4plVeQGJusXHyMxW8NV/VAkyMNZ5sS/8nkJY0hU+lj F/tL6bd17xjHK0/qQHu4OgnGjeyb9Yw== X-Google-Smtp-Source: AGHT+IFOdvxwMncof6lisrmPi7QAgqGGVtkVkbMp8UmAenh6ssjFRzdaVr9603GI5wfm7xnM98gZQwFwoKe4Y1qsNpU= X-Received: by 2002:a05:6870:b253:b0:259:8371:513f with SMTP id 586e51a60fabf-25983715724mr790830fac.21.1718735242340; Tue, 18 Jun 2024 11:27:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Tue, 18 Jun 2024 14:27:10 -0400 Message-ID: Subject: Re: Seeking Clarification on Function Definitions in PostgreSQL Extensions To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000095317f061b2e3bbb" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000095317f061b2e3bbb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jun 18, 2024 at 1:57=E2=80=AFPM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Tuesday, June 18, 2024, Ron Johnson wrote: > >> >> But I stand by returning OUT params and records at the same time. >> > > You mean you dislike adding the optional returns clause when output > parameters exist? > Correct. It breaks the distinction between function and procedure. > Because the out parameters and the =E2=80=9Crecord=E2=80=9D represent the= exact same thing. > What's the purpose? Legacy of not having procedures? --00000000000095317f061b2e3bbb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Jun 18, 2024 at 1:57=E2=80=AFPM D= avid G. Johnston <david.g.= johnston@gmail.com> wrote:
On Tuesday, June 18, 2024, Ron= Johnson <r= onljohnsonjr@gmail.com> wrote:

But I stand by returning OUT params and records at the sam= e=C2=A0time.

You mean you= dislike adding the optional returns clause when output parameters exist?= =C2=A0

Correct.=C2=A0 It breaks the = distinction between function and procedure.
=C2=A0
Because the out parameters an= d the =E2=80=9Crecord=E2=80=9D represent the exact same thing.
=C2=A0
What's the purpose?=C2=A0 Legacy of not hav= ing procedures?=C2=A0



--00000000000095317f061b2e3bbb--