Re: PQexecParams, placeholders and variable lists of params - Mailing list pgsql-general

From David G. Johnston
Subject Re: PQexecParams, placeholders and variable lists of params
Date
Msg-id CAKFQuwbjD0jokC3WBJ-TcCXtXuW=pHDknZOKSBQ2tLtVm+um7w@mail.gmail.com
Whole thread Raw
In response to Re: PQexecParams, placeholders and variable lists of params  (tomas@tuxteam.de)
Responses Re: PQexecParams, placeholders and variable lists of params  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, Nov 23, 2021 at 7:21 AM <tomas@tuxteam.de> wrote:
Makes sense. Problem is, that, again, the application would be
responsible of making sure the individual values don't contain nasty
stuff (for example, if they are strings) before consolidating them to
one PostgreSQL array literal.


So long as you actually pass the literal value via a parameter the worst problem you can have is a syntax error in converting the literal into whatever type is being cast to.

I personally tend to just build up a CSV-like string (my data is usually controlled enough the using the pipe symbol as a separator alleviates escaping concerns) and using string_to_array($1,'|') to get the array of values into the query.

David J.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Max connections reached without max connections reached
Next
From: Tom Lane
Date:
Subject: Re: PQexecParams, placeholders and variable lists of params