#15130: Model.validate_unique method is not considered with multi-db
--------------------------------------+-------------------------------------
Reporter: t2y | Owner:
Status: new | Milestone: 1.3
Component: ORM aggregation | Version: 1.2
Resolution: | Keywords: multi-db
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by kmtracey):
* needs_tests: 0 => 1
* milestone: => 1.3
Comment:
Replying to [comment:1 adamnelson]:
> This looks like a problem on the current milestone:1.2 and therefore is
too late for milestone:1.3
? We're not to the point of pushing bug-fixes out of 1.3 yet, I don't
think. Features, yes, are no longer appropriate for the 1.3 milestone. But
the description and the word "problem" there make this sound like a bug,
not a feature. If it's been around since 1.2 it wouldn't be classified as
a blocking bug, but it can still be in the milestone for 1.3. (Which does
not guarantee it will get fixed for 1.3, but still it's not correct at
this point to say a fix for this could not be put it for 1.3)
--
Ticket URL: <http://code.djangoproject.com/ticket/15130#comment:2>
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 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.
