Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1j0Fyb-0005AE-Tk
	for pgsql-admin@arkaria.postgresql.org; Sat, 08 Feb 2020 02:36:10 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1j0Fya-0002lo-N2
	for pgsql-admin@arkaria.postgresql.org; Sat, 08 Feb 2020 02:36:08 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1j0Fya-0002lh-Dh
	for pgsql-admin@lists.postgresql.org; Sat, 08 Feb 2020 02:36:08 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1j0FyY-0005UD-Dj
	for pgsql-admin@postgresql.org; Sat, 08 Feb 2020 02:36:08 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 0182a38N031015;
	Fri, 7 Feb 2020 21:36:03 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: plpgsql, dynamic variable lengths..
In-reply-to: 
 <CAOC+FBVj-CuZriMmLa0oEWONuQQmzzLN9Bzu8cF6AGykh+OUmA@mail.gmail.com>
References: 
 <CAOC+FBVDAcHKJXfJhYVf4Et5E6ohbE+Sw4s2jG+ioCCLJOjunw@mail.gmail.com>
 <29969.1581127784@sss.pgh.pa.us>
 <CAOC+FBVj-CuZriMmLa0oEWONuQQmzzLN9Bzu8cF6AGykh+OUmA@mail.gmail.com>
Comments: In-reply-to Wells Oliver <wells.oliver@gmail.com>
	message dated "Fri, 07 Feb 2020 18:23:31 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <31013.1581129363.1@sss.pgh.pa.us>
Date: Fri, 07 Feb 2020 21:36:03 -0500
Message-ID: <31014.1581129363@sss.pgh.pa.us>
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

Wells Oliver <wells.oliver@gmail.com> writes:
> Yes, but the issue is it won't always be three params, and not always the
> same variable in $1, $2, etc. It depends on which keys are present in the
> passed JSON object. Which I why I think I need to do something else like
> create a recordset and pass that in USING, or something. Just can't quite
> figure it out...

Maybe just pass the JSON object as the only USING param, and do the
field selections in the SQL fragments?

			regards, tom lane