, but it would probably require some significant work, since
you'd have to transform SELECT statements into FETCH statements.
anyway, thanks for the fix!
On Sep 26, 8:01 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On Sep 26, 2007, at 5:31 PM, Dan Watson wrote:
cursor.description isn't available after
It seems that something changed in 0.4 that causes server-side cursors
(in postgresql) to fail. I'm issuing the DECLARE/FETCH commands
manually through connection.execute, not using server_side_cursors in
the dialect, since I only want certain queries to use them. I verified
that this works on
, and leave the SS cursor positioned
before the first row.
On Sep 26, 4:34 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On Sep 26, 2007, at 3:52 PM, Dan Watson wrote:
It seems that something changed in 0.4 that causes server-side cursors
(in postgresql) to fail. I'm issuing the DECLARE/FETCH
Right now, importing sqlalchemy on python 2.3 is broken. __name__ is
readonly in 2.3, so the import fails:
from sqlalchemy import *
Traceback (most recent call last):
File stdin, line 1, in ?
File /home/watsond/python_packages/sqlalchemy/__init__.py, line 9,
in ?
from sqlalchemy.schema
