psycopg/psycopg2
1
1
Fork 0
mirror of https://github.com/psycopg/psycopg2.git synced 2025-03-03 15:45:46 +03:00
Code Issues Packages Projects Releases Wiki Activity

Asynchronous queries marked as experimental.

Browse Source
This commit is contained in:
Daniele Varrazzo 2010-02-09 19:59:01 +00:00 committed by Federico Di Gregorio
parent 4708704f16
commit 5c732ac2a3
1 changed files with 3 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/advanced.rst
View File

@ -225,11 +225,10 @@ Asynchronous queries
.. warning:: .. warning::
Asynchronous queries are not enabled for 2.0 Psycopg support for asynchronous queries is still experimental and the
informations reported here may be out of date.
.. todo:: Discussion testing and suggestions are welcome.
I think this is false now: async queries seem working right now...
Program code can initiate an asynchronous query by passing an ``async=1`` flag Program code can initiate an asynchronous query by passing an ``async=1`` flag
to the :meth:`cursor.execute` or :meth:`cursor.callproc` methods. A very to the :meth:`cursor.execute` or :meth:`cursor.callproc` methods. A very
@ -252,10 +251,6 @@ a number of different ways:
The return value is ``True`` if the query was successfully aborted or The return value is ``True`` if the query was successfully aborted or
``False`` if it was executed. Query result are discarded in both cases. ``False`` if it was executed. Query result are discarded in both cases.
.. todo::
Can't see any ``connection.cancel`` method.
3) :meth:`cursor.execute` is called again on the same cursor 3) :meth:`cursor.execute` is called again on the same cursor
(:obj:`.execute()` on a different cursor will simply raise an exception). (:obj:`.execute()` on a different cursor will simply raise an exception).
This waits for the complete execution of the current query, discard any This waits for the complete execution of the current query, discard any