#8377: unique_for_date (model field option) doesn't work
-------------------------------------------------------------+--------------
          Reporter:  Bela Hausmann <[EMAIL PROTECTED]>  |         Owner:  nobody
            Status:  new                                     |     Milestone:   
     
         Component:  django.contrib.admin                    |       Version:  
SVN   
        Resolution:                                          |      Keywords:   
     
             Stage:  Unreviewed                              |     Has_patch:  
0     
        Needs_docs:  0                                       |   Needs_tests:  
0     
Needs_better_patch:  0                                       |  
-------------------------------------------------------------+--------------
Comment (by gabor):

 i agree that the whole model-aware validation will fix this,
 (and have read the thread at http://groups.google.com/group/django-
 developers/browse_thread/thread/997c0c5eb36eb4f4/8825c573c111c176 )

 but please note, that "unique_together" seems to work correctly. so if
 that can work without validation-aware-models,
 this one should be able to work too.. (at least imho)

 so, the question is: if someone submits a patch for this, will it get
 included (and added to 1.0.x), or
 the plan is to wait for salvation (validation-aware-models and 1.1.x)

 if the answer is the waiting-for-validation-aware-models, then perhaps a
 note should be added to the documentation,
 or a known-bugs document should be created (or is there one? i couldn't
 find it)

 p.s: this whole "unique" situation is quite painful. i mean, we have
 documentation that documents an attribute
 as working, while a quick "{{{ grep unique_for_date * -r}}}" shows that
 the only place where the attribute is mentioned is when the field-object
 accepts it and stores it inside :-(

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8377#comment:4>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to