Re: [sqlalchemy] How to refer to a live SA transaction from subsequent requests

2011-12-18 Thread Andronikos Nedos
On Saturday, 17 December 2011 19:57:10 UTC, Michael Bayer wrote: On Dec 17, 2011, at 2:24 PM, Andronikos Nedos wrote: So, if I understand correctly, I need to maintain the Connection object between requests and on the 2nd request bind a session to the existing Connection object

[sqlalchemy] How to refer to a live SA transaction from subsequent requests

2011-12-17 Thread Andronikos Nedos
Hi all, We make heavy use of SqlAchemy in our app and use a custom 2-phase commit protocol over HTTP to communicate with mobile devices. While all read,write,deletes happen in a first HTTP request, a subsequent HTTP request needs to find the transaction and either commit or abort. i.e.,

Re: [sqlalchemy] How to refer to a live SA transaction from subsequent requests

2011-12-17 Thread Andronikos Nedos
On Saturday, 17 December 2011 17:22:26 UTC, Michael Bayer wrote: On Dec 17, 2011, at 9:04 AM, Andronikos Nedos wrote: Hi all, We make heavy use of SqlAchemy in our app and use a custom 2-phase commit protocol over HTTP to communicate with mobile devices. While all read,write,deletes

Re: [sqlalchemy] StaleDataError when deleting through an association_proxy

2011-02-03 Thread Andronikos Nedos
assuming Dtable.data_id references BTable. There's a few ways to go about this. The usual way to alter what gets deleted where in a flush is to use SessionExtension.before_flush() to figure out whatever needs to happen based on the pending state of things, using Session.delete() to

[sqlalchemy] StaleDataError when deleting through an association_proxy

2011-02-01 Thread Andronikos Nedos
Hi all, This is a slightly complicated problem, which I'm not sure how to tackle. I get a StaleDataError: UPDATE statement on table 'D' expected to update 1 row(s); 0 were matched. in the following setup and action sequence: Setup: I have defined an association_proxy - named 'tasks' - from

[sqlalchemy] Re: versioning when updating a relationship

2010-12-22 Thread Andronikos Nedos
The versioning example appears to be cautious about determining if there was a net change present.    The good news is that we don't actually need the new value of customer_ref when we create the historical entry, we need the current entry, which should be present in the object's dict.  

[sqlalchemy] versioning when updating a relationship

2010-12-20 Thread Andronikos Nedos
Hi all, I'm retrofitting the SA versioning example [http://www.sqlalchemy.org/ docs/orm/examples.html#versioned-objects] into a large TG2 webapp. Since I would like to make versioning transparent to the existing controller's code, I would like a new version to be emitted when I update a

[sqlalchemy] list returning attribute and SA

2010-06-28 Thread Andronikos Nedos
Hi, I'm wondering if SA can help in the following situation. I'm trying to store a schedule which can be reduced to an id and a recurrence rule encoded as an rrule from python-dateutil. Something like the following: schedule = Table('schedules_table', meta, Column('id', Integer,