On Tue, Mar 6, 2012 at 12:21, Martin Ostrovsky
wrote:
> Danny reading your reply gave me an idea to try and it worked.
>
> I switched the order of the inlines. So I put C first, then B. This way C
> validates properly, then B is deleted and the cascaded deletion deletes C
> and everything works as
Danny reading your reply gave me an idea to try and it worked.
I switched the order of the inlines. So I put C first, then B. This way C
validates properly, then B is deleted and the cascaded deletion deletes C
and everything works as expected.
On Monday, March 5, 2012 6:15:18 PM UTC-5, Danny W
On Tue, Mar 6, 2012 at 12:06, Martin Ostrovsky
wrote:
>[...]
> Now I get what's happening (I think), B gets deleted first, then the formset
> validation for C runs, tries to validate the drop down choice, and fails
> since B has already been deleted.
>
> What do you guys think? Is this a bug or a
Hello,
I have come across this issue in Django v1.2.5, just test it on 1.4rc1 and
can still reproduce. Not sure if it's a bug or a case of "don't do that".
But here goes.
Here's the models.py:
http://pastebin.com/8QU9dkYd
Here's the admin.py:
http://pastebin.com/JGFu5nhv
So what we have are
We're nearly there!
The Django 1.4 release candidate package is now available, and you can
read all about it on the blog:
https://www.djangoproject.com/weblog/2012/mar/05/14-rc-1/
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message be
