On Feb 28, 2011, at 1:26 AM, Chris Withers wrote:
> On 27/02/2011 23:20, Michael Bayer wrote:
>> hmm ! not really actually.
>
> No probs, I thought that'd be a bit of a stretch ;-)
>
>> Also, some deletes, such as for de-associated orphans, don't get added to
>> "delete" until after before_f
On 27/02/2011 23:20, Michael Bayer wrote:
hmm ! not really actually.
No probs, I thought that'd be a bit of a stretch ;-)
Also, some deletes, such as for de-associated orphans, don't get added to
"delete" until after before_flush().
Hmm, does this imply that the versioning recipes that
hmm ! not really actually. Also, some deletes, such as for de-associated
orphans, don't get added to "delete" until after before_flush().
On Feb 27, 2011, at 4:00 PM, Chris Withers wrote:
> Hi All,
>
> In the before_flush of a SessionExtension, is there any way I can tell if an
> object
Hi All,
In the before_flush of a SessionExtension, is there any way I can tell
if an object is in session.deleted as a result of being deleted in its
own right or as a result of being cascaded from the delete of another
object?
cheers,
Chris
--
Simplistix - Content Management, Batch Proces
hi
i have some pre_save automatic operations and decided MVC-like to
split them into 2 phases - a per-object validation-only that goes at
save(), and a per-flush set-up 2nd phase for putting timestamps etc.
The 2nd one is via SessionExtension.before_flush().
i'm looking at the session state at
Foreword: sqlalchemy is really amazing!
Hello,
I'm trying to build a database where users become aware of what has been
changed by other users: there is a SessionExtension that collects info about
changes and then dispatch some messages with a Pyro Event Server.
I'm trying to understand what
