Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
-+-
 Reporter:  wdoekes  |Owner:  Alex
 Type:  Uncategorized|   Status:  closed
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  unique_for_date  | Triage Stage:  Ready for
  unique_for_month unique_for_year   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Please do not reopen bugs fixed 4 years ago. Create a new ticket where you
 can reference this one, thanks.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
-+-
 Reporter:  wdoekes  |Owner:  Alex
 Type:  Uncategorized|   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  unique_for_date  | Triage Stage:  Ready for
  unique_for_month unique_for_year   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by monuszko):

 * status:  closed => new
 * severity:   => Normal
 * cc: monuszko (added)
 * needs_better_patch:  0 => 1
 * version:  master => 1.4
 * easy:   => 0
 * type:   => Uncategorized
 * ui_ux:   => 0
 * resolution:  fixed =>


Comment:

 I stumbled upon the same problem. I'm using Python 2.7.3 and Django
 1.4.5-1 from Debian repositories. I can add multiple entries with
 identical values and the admin interface doesn't complain. I tried with
 both 'slug' and 'title'.

 {{{

 # models.py

 from django.db import models

 from django.utils.timezone import now as utcnow
 now = utcnow() # replacing - date.now() causes problems with auto_now_add

 class Entry(models.Model):
 created_at = models.DateTimeField(default=now, editable=False)
 title  = models.CharField(max_length = 50)
 content= models.TextField()
 slug   = models.SlugField(unique_for_date='created_at')

 def __unicode__(self):
 return self.title
 class Meta:
 ordering = ['-created_at']

 # admin.py

 from news.models import Entry
 from django.contrib import admin

 class EntryAdmin(admin.ModelAdmin):
 prepopulated_fields = {'slug': ('title',)}

 list_filter = ['created_at']
 date_hierarchy = 'created_at'

 admin.site.register(Entry, EntryAdmin)

 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
+---
  Reporter:  wdoekes| Owner:  Alex  
  
Status:  closed | Milestone:  1.1   
  
 Component:  Forms  |   Version:  SVN   
  
Resolution:  fixed  |  Keywords:  unique_for_date 
unique_for_month unique_for_year
 Stage:  Ready for checkin  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 Replying to [comment:13 shannon]:
 > does this not also resolve #8377?
 Looks like it.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
+---
  Reporter:  wdoekes| Owner:  Alex  
  
Status:  closed | Milestone:  1.1   
  
 Component:  Forms  |   Version:  SVN   
  
Resolution:  fixed  |  Keywords:  unique_for_date 
unique_for_month unique_for_year
 Stage:  Ready for checkin  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Comment (by shannon):

 does this not also resolve #8377?

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
---+
  Reporter:  wdoekes   | Owner:  Alex   
 
Status:  new   | Milestone:  1.1
 
 Component:  Forms |   Version:  SVN
 
Resolution:|  Keywords:  unique_for_date 
unique_for_month unique_for_year
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by Alex):

 That comment was supposed to say, "long function is no longer long" so as
 to be witty, now I just sound like an idiot :/

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
---+
  Reporter:  wdoekes   | Owner:  Alex   
 
Status:  new   | Milestone:  1.1
 
 Component:  Forms |   Version:  SVN
 
Resolution:|  Keywords:  unique_for_date 
unique_for_month unique_for_year
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * component:  Database layer (models, ORM) => Forms

Comment:

 Model Validaiton isn't making it in for 1.1 so this is just going to be
 solved in forms.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
---+
  Reporter:  wdoekes   | Owner:  Alex   
 
Status:  new   | Milestone:  1.1
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
unique_for_date unique_for_month unique_for_year
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * owner:  nobody => Alex

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
---+
  Reporter:  wdoekes   | Owner:  nobody 
 
Status:  new   | Milestone:  1.1
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
unique_for_date unique_for_month unique_for_year
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: flo...@gmail.com (added)

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
---+
  Reporter:  wdoekes   | Owner:  nobody 
 
Status:  new   | Milestone:  1.1
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
unique_for_date unique_for_month unique_for_year
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by Horst Gutmann ):

 * cc: ze...@zerokspot.com (added)

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
---+
  Reporter:  wdoekes   | Owner:  nobody 
 
Status:  new   | Milestone:  1.1
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
unique_for_date unique_for_month unique_for_year
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.1

Comment:

 I think we need a similar stop-gap to unique_together for unique_for_date
 in 1.1.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
---+
  Reporter:  wdoekes   | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
unique_for_date unique_for_month unique_for_year
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by Alex):

 Karen you're right about this, I'll add it to the model-validation wiki
 and bring it up with Honza this evening if he's on.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10134: unique_for_* broken?

[Django]

#10134: unique_for_* broken?
---+
  Reporter:  wdoekes   | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
unique_for_date unique_for_month unique_for_year
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This would be one of the things lost in the move from the old
 forms/manipulators structure to new forms.  The implementation/enforcement
 of the parameter was removed, but not the ability to specify it, since (I
 believe) the intent was for the check to only be MIA for as long as model
 validation (#6845) was missing.  Model validation was hoped to be included
 in 1.0, but unfortunately it is still not in trunk.

 Furthermore, from what I can glean of the current implementation at
 http://github.com/HonzaKral/django/tree/model-validation the check for
 these parameters is not yet handled by model validation, either, so I'm
 going to leave this open rather than closing it as a dup of #6845.  From
 what I can tell restoration of checks for parameters like this is not
 currently covered by #6845, nor do I see it on any of the open issues/todo
 type pages, so this ticket can serve as a tracker for restoring this
 function which seems to have slipped through the cracks somewhere.  (For
 anyone more up-to-speed on model validation, if I'm wrong about this bit
 being missing, or for that matter if I'm wrong about this function
 intending to be re-supported via model validation, feel free to correct
 me.)

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---