postgresql: executing stored procedures with bind parameters fails

[Moritz Heidkamp]

Executing a stored procedure with bind parameters in argument position like this:

(query conn "EXECUTE foo($1, $2)" 100 2)

Leads to an error like this:

ERROR: bind message supplies 2 parameters, but prepared statement "" requires 0

Adding explicit types after the parameters (like $1::int) doesn't work either.

[sjamaan]

This is actually an inconsistency/bug in postgresql (see ​this mail exchange).

It is now possible (postgresql trunk) to provide the name of a prepared statement (which is what EXECUTE runs, not stored procedures) as a symbol to query instead of a string query.

[felix winkelmann]

Milestone 4.8.0 deleted