On Tue, Oct 21, 2008 at 12:36 PM, bobhaugen <[EMAIL PROTECTED]> wrote:
> > On Oct 21, 10:59 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > > Have you tried whatever scenario you are particularly interested in on > 1.0 > > or current code? > > > > Though general model validation did not make it into 1.0, checking of > unique > > and unique_together was added in changeset [8805]. It may not cover the > > inline/missing parent foreign key value case, though -- I haven't tried > > that. > > Karen, thanks for the reply. But no luck. > > Just downloaded revision 9240. > > Tried unique_together constraint in admin both plain and with a form > that overrode clean(). > Parent foreign key value is still None. Can't check unique_together. > 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/6143408977f7ad/d09c52e1fb561469 ? If the case you are interested in isn't covered by the current patch and is not called out as something that isn't handled yet in the status (which I have not read closely, so I don't know one way or the other) you might want to bring it up as an issue either in the ticket or as a response to that status note. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
