Re: "unique_together" only validated in modelform.is_valid() if ALL of the referenced fields (Ticket #13091)

On 04/22/2011 02:42 AM, legutierr wrote: > However, in the case of a tuple of fields that are "unique together", > the proper behavior should be that if *any* of those fields are > editable in the form, the constraint should be validated by > is_valid(). In the current implementation, *all* of

Re: [5-for-1] Review request

I noticed the "TODO" on the bottom of that page you linked... if you actually want to write something up for the docs about reviewing tickets (based on the discussion that's happened on the list the last few days) I'd suggest adding it to the /docs/howto/contribute section. Feel free to ping

Re: [5-for-1] Review request

On Fri, Apr 22, 2011 at 3:26 AM, Aymeric Augustin wrote: > I have retroactively added 5 tickets for Alex's review, plus 5 tickets that > I'd like to trade against a review of #15255, especially the second comment. Done! BTW, I'm pretty sure Alex was joking

sitemaps and prepend_www

Hi, I cannot use www in current_site.domain since .domain is used in many places (e.g. emails) where www is not required. BTW, I'm using PREPEND_WWW=True setting, since it makes url looks better. Now, google webmaster tools rejecting all links in sitemap of my project because lack of 'www'. My

Re: Policy for Duplicate Tickets - Bug vs. Feature Request

On Thu, 21 Apr 2011 21:33:45 -0500, Jacob Kaplan-Moss wrote: > That's more or less how I look at things, with one additional caveat: Thanks for the clarification, Jacob. Kind regards Michael -- You received this message because you are subscribed to the Google Groups

Re: [5-for-1] Review request

2011/4/21 Alex Gaynor > As did I, do we have to retroactively require more reviews ;) > I'm now tracking my 5-for-1 deals here: http://myks.org/stuff/django_5-for-1.txt I have retroactively added 5 tickets for Alex's review, plus 5 tickets that I'd like to trade against

"unique_together" only validated in modelform.is_valid() if ALL of the referenced fields are included in the form (Ticket #13091)

The subject didn't make any sense. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to

"unique_together" only validated in modelform.is_valid() if ALL of the referenced fields (Ticket #13091)

Thanks for your response, Florian. > > modelform.is_valid() fails to anticipate database integrity errors > > when those errors involve any fields that are not part of that form > > itself. > > That is wanted behaviour, eg consider my workflow: > > class SomeForm(ModelForm): >   class Meta: >