On Feb 12, 2014, at 1:49 AM, Wolfgang Schnerring wrote:
> On 11 Feb 2014 06:54:22 Michael Bayer wrote:
>> On Feb 11, 2014, at 3:44 AM, Wolfgang Schnerring wrote:
>>> parent = session.query(Parent).first()
>>> self.assertEqual(1, len(parent.children))
>>> session.begin_nested(
On Feb 11, 2014, at 3:44 AM, Wolfgang Schnerring wrote:
>def test_children_should_be_removed_from_collection_on_savepoint(self):
>session = self.sessionmaker()
>parent = Parent()
>Child(parent=parent)
>session.add(parent)
>session.commit()
>
>
On Feb 3, 2014, at 2:39 AM, Wolfgang Schnerring wrote:
>
> I guess I didn't make it clear enough that I'm talking mainly about
> this collections issue. Sorry about that; let me try again:
> I feel it would be much more convenient if the state achieved by a savepoint
> was reflected by collecti
On Jan 31, 2014, at 9:27 AM, Wolfgang Schnerring wrote:
> Hello list,
>
> pardon the innocent/dumb question: wouldn't it make sense to expire_all()
> on begin_nested() and rollback()?
>
> My concrete example goes like this:
>
> savepoint = session.begin_nested()
> session.delete(stuff)
> s
Hello list,
pardon the innocent/dumb question: wouldn't it make sense to expire_all()
on begin_nested() and rollback()?
My concrete example goes like this:
savepoint = session.begin_nested()
session.delete(stuff)
session.begin_nested()
# Now, if I don't call session.expire_all() here, st
