On Sunday 26 February 2006 03:15, Russell Keith-Magee wrote:
> Interesting... by way of diagnosis, it might be helpful to dump the
> contents of seen_objs that is collected just before the call to
> delete_objects() at line 216 of django/core/db/query.py. That
> structure determines the order in
On 2/25/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> On Friday 24 February 2006 23:34, Russell Keith-Magee wrote:
> > Can you confirm that your problem is also resolved?
>
> Thanks for working on this, but unfortunately it's still not resolved.
> However, I've found I've got the same problem wit
On Friday 24 February 2006 23:34, Russell Keith-Magee wrote:
> On 2/19/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> > On 2/19/06, Luke Plant <[EMAIL PROTECTED]> wrote:
> > > I think I've found a bug in bulk delete.
> >
> > Other than that -
On 2/19/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On 2/19/06, Luke Plant <[EMAIL PROTECTED]> wrote:
> >
> > I think I've found a bug in bulk delete.
>
> Other than that - I'll look into it.
Hi Luke,
I have put together a test case us
Hi Luke,
On 2/19/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> I think I've found a bug in bulk delete.
This looks very similar to a bug I have been chasing where the query
system mistakes a m2m field for a m2o field (because of names reported
by get_accessor_name()).
What SVN
Hi Russell,
I think I've found a bug in bulk delete. It doesn't occur with mysql,
only with Postgres (perhaps because Django doesn't output the same
constraints as it does with Postgres).
A simplified but hopefully adequate version of my model is below:
class Person(models.M
