Wells Oliver <wells.oliver@xxxxxxxxx> 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
