You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the pgdb module and the query_formatted() and higher level methods of the pg module such as update(), input parameters are adapted automatically, e.g. converting Python lists to PostgreSQL arrays.
However, the lower level query() and query_prepared() methods of the pg module pass parameters in raw form. This is not well documented, and there is no help on what to do in this case. We should explain how and when to manually adapt the parameters. Maybe also provide alternative low level methods with the Postgres parameter syntax or improve the low level methods so that they automatically adapt parameters as well if that's possible without loss of performance or backward compatibility.
(copied from Trac ticket 81, created 2019-06-07)
The text was updated successfully, but these errors were encountered:
In the
pgdb
module and thequery_formatted()
and higher level methods of thepg
module such asupdate()
, input parameters are adapted automatically, e.g. converting Python lists to PostgreSQL arrays.However, the lower level
query()
andquery_prepared()
methods of thepg
module pass parameters in raw form. This is not well documented, and there is no help on what to do in this case. We should explain how and when to manually adapt the parameters. Maybe also provide alternative low level methods with the Postgres parameter syntax or improve the low level methods so that they automatically adapt parameters as well if that's possible without loss of performance or backward compatibility.(copied from Trac ticket 81, created 2019-06-07)
The text was updated successfully, but these errors were encountered: