From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: plpgsql, dynamic variable lengths.. |
Date: | 2020-02-08 08:54:45 |
Message-ID: | CAECtzeWwRbMV5eXSdyt+SnDD_VhN6vdiRkjpbHjSq0Lg_N16qg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Le sam. 8 févr. 2020 à 03:36, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> a écrit :
> Wells Oliver <wells(dot)oliver(at)gmail(dot)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?
>
>
And why don't you do this instead?
SQLSTRING := SQLSTRING || ' AND col1 = ' || quote_literal(args->>'col1');
--
Guillaume.
From | Date | Subject | |
---|---|---|---|
Next Message | Wells Oliver | 2020-02-08 20:41:13 | Re: plpgsql, dynamic variable lengths.. |
Previous Message | Tom Lane | 2020-02-08 02:36:03 | Re: plpgsql, dynamic variable lengths.. |