Upon reviewing my code this morning it appears that I forgot to fix
the scalar method. Updated patch attached.
~ Daniel
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group,
On Jan 24, 2007, at 8:17 AM, Daniel Miller wrote:
Yeah, I know that's ugly. However, its definitely more visual
overhead than actual overhead. Not to mention (as was said on the
psycopg list) fetchone() should not be used many times in succession.
but ResultProxy is used for every database,
Michael Bayer wrote:
ive heard of this one already, which is why the option is turned off.
unfortunately I cant reproduce that here, so until someone wants to
figure out whats going on with that, not sure what I can do.
Tell me what I have to do. Here I have debian etch and pg 8.1.(the last
Michael Bayer wrote:
ive heard of this one already, which is why the option is turned off.
unfortunately I cant reproduce that here, so until someone wants to
figure out whats going on with that, not sure what I can do.
After some tries, I see that is I wrote (very bad code line):
I think I was the original person who had this problem. I found a bit
of time to troubleshoot it and came up with a patch.
The problem seems to be in ResultProxy when it does the metadata =
cursor.description bit. cursor.description is returning None because
the cursor has not had any rows
ugh, adds an extra conditional into every fetchone() :)
On Jan 23, 2007, at 10:06 PM, Daniel Miller wrote:
I think I was the original person who had this problem. I found a bit
of time to troubleshoot it and came up with a patch.
The problem seems to be in ResultProxy when it does the
