Re: plpgsql, dynamic variable lengths.. - Mailing list pgsql-admin

From Guillaume Lelarge
Subject Re: plpgsql, dynamic variable lengths..
Date
Msg-id CAECtzeWwRbMV5eXSdyt+SnDD_VhN6vdiRkjpbHjSq0Lg_N16qg@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql, dynamic variable lengths..  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: plpgsql, dynamic variable lengths..
List pgsql-admin
Le sam. 8 févr. 2020 à 03:36, Tom Lane <tgl@sss.pgh.pa.us> a écrit :
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?


And why don't you do this instead?

SQLSTRING := SQLSTRING || ' AND col1 = ' || quote_literal(args->>'col1');


--
Guillaume.

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: plpgsql, dynamic variable lengths..
Next
From: Wells Oliver
Date:
Subject: Re: plpgsql, dynamic variable lengths..