OK, this is interesting: I didn't mention that I also has
limit_choices_to set on the self-referential foreign key. When I
remove limit_choices_to the problem goes away! My model is listed
below. I had set limit_choices_to=PARENT_CHOICES on OrgUnit.parent.
[start code]
LIBRARY_ID = 1
SAP_ORG_UNIT
On Mon, 2008-08-25 at 17:44 -0700, dchandek wrote:
> To make this even stranger, the problem only occurs when the pk of the
> selected (self-)related object is 1. There's something deep going on
> in Django that I can't trace ...
This is going to be infinitely easier to debug if have a small exa
To make this even stranger, the problem only occurs when the pk of the
selected (self-)related object is 1. There's something deep going on
in Django that I can't trace ...
--David
On Aug 25, 4:20 pm, dchandek <[EMAIL PROTECTED]> wrote:
> After upgrading from post-0.96 development version to 1.0
After upgrading from post-0.96 development version to 1.0-beta1, I now
get a MultipleObjectsReturned when submitting a change via the Admin
UI to an object, where the model has a many-to-one relationship with
itself. From the Python interactive prompt I am not able to reproduce
the error.
Traceba
4 matches
Mail list logo
