the new data isn't visible to the other
process if the updating process still has a cursor live?
--
david bonner
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group
into pdb, the data in instance.notes looks
like the new value, but querying the db in a separate process gets me
the old value.
--
david bonner
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy
oops, uncommenting the pdb.set_trace(), obviously. sorry.
class MyExtension (MapperExtension) :
def after_update (self, mapper, connection, instance) :
#pdb.set_trace()
pprint.pprint(instance)
return EXT_CONTINUE
--
david bonner
[EMAIL PROTECTED
the flush?
--
david bonner
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email
into that.
and thanks again for the amazingly-quick and helpful replies.
--
david bonner
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy
the MapperExtension
incorrectly?
Any help would be greatly appreciated. Thanks.
--
david bonner
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy
sqlalchemy.orm.object_mapper(foo).local_table.name
--
david bonner
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from
Hi, I've run into a problem running SA 0.4.0 on top of psycopg2. We
had a DNS hiccup, and the next attempt to execute a query triggered a
ProgrammingError. Unfortunately, it seems that error didn't also
invalidate the (implicit) connection, which was then returned to the
pool.
Successive
On Dec 4, 4:32 pm, Michael Bayer [EMAIL PROTECTED] wrote:
if the error message isnt caught by is_disconnect(), then yes the
specific error message should be installed in there. But also note
that psycopg2 has some specific issues with disconnects, namely that
the exception is not always