Sweet thanks for the quick fix as always.
On Tue, Jan 4, 2011 at 11:01 AM, Michael Bayer wrote:
> ah you were right the first time. The "all" concept is local dependency.py,
> which just needs to interpret its internal values appropriately before
> sending arguments off to attributes.py.
>
>
ah you were right the first time. The "all" concept is local dependency.py,
which just needs to interpret its internal values appropriately before sending
arguments off to attributes.py.
On Jan 4, 2011, at 10:49 AM, Will Weaver wrote:
> I made a different patch. This one I don't believe is
On Jan 4, 2011, at 8:58 AM, Will wrote:
> Hello,
>
> I noticed that when setting passive_deletes="all" on a relationship
> and try to delete the parent object sqlalchemy still tries to query
> the child object. For the way my models are set up I can't have the
> child object be queried. I'm us
I made a different patch. This one I don't believe is ideal, but I
think it might be the appropriate place to make the patch
http://pastebin.com/kZbZcJ3u
On Tue, Jan 4, 2011 at 8:58 AM, Will wrote:
> Hello,
>
> I noticed that when setting passive_deletes="all" on a relationship
> and try to del
Hello,
I noticed that when setting passive_deletes="all" on a relationship
and try to delete the parent object sqlalchemy still tries to query
the child object. For the way my models are set up I can't have the
child object be queried. I'm using a hybrid of horizontal and
vertical sharding in th
