On Tue, Oct 21, 2008 at 2:35 PM, bobhaugen <[EMAIL PROTECTED]> wrote:
> > On Oct 21, 12:34 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > > Well then the next step I would try is testing out the current patch for > > general model validation, which is ticket #6845: > > > > http://code.djangoproject.com/ticket/6845 > > > > Status on this was most recently reported here, I think: > > > > http://groups.google.com/group/django-developers/browse_thread/thread... > > That status message says: > > known Issues > > ========================= > > > > * InlineFormSet.save_as_new is broken > > I do see a change in the last patch > http://code.djangoproject.com/attachment/ticket/6845/6845-against-9226.diff > for BaseGenericInlineFormSet, to preserve the parent foreign key for > validation. > But I don't think that's what Admin uses. > I don't know -- this isn't a case I've looked at, and I haven't tried that patch myself yet. One other ticket I just noticed that you might want to keep an eye on is: http://code.djangoproject.com/ticket/8882 That may be the exact case you are concerned with and it may get fixed sooner than overall model validation gets into the code, but I'm just guessing, since I'm not actually working on either of them myself. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
