#76: Support and document usage of prepared statements
---------------------------------+----------------------
Reporter: cito | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 5.1
Component: Classic and DB API | Version: 5.0
Resolution: | Keywords: prepared
---------------------------------+----------------------
Comment (by cito):
Note that executing prepared statements already works with this
workaround:
{{{
db.query('prepare c AS INSERT INTO tweets VALUES($1,$2,$3)')
db.query_formatted('execute c(%s,%s,%s)', [45, 'trump', 'so sad'],
inline=True)
}}}
But it doesn't work with inline=False (or db.query for that matter).
It would be nice to have special prepare(), exec_prepared(),
descrive_prepared() and delete_prepared() methods for working with
prepared statements, which use the corresponding C functions
(delete_prepared() would use deallocate, it doesn't have a corresponding C
function).
--
Ticket URL: <http://trac.pygresql.org:8000/pgtracker/ticket/76#comment:1>
PyGreSQL <http://www.pygresql.org/>
PyGreSQL Tracker
_______________________________________________
PyGreSQL mailing list
[email protected]
https://mail.vex.net/mailman/listinfo/pygresql
