#23416: Django 1.7 fails to output a CHECK constraint on PositiveIntegerFields
using postgres backend
-------------------------------------+-------------------------------------
Reporter: ris | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.7
(models, ORM) | Resolution: fixed
Severity: Release blocker | Triage Stage: Ready for
Keywords: postgres check | checkin
constraint positiveintegerfield | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Marc Tamlyn <marc.tamlyn@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"14c8456ffe7e6388383e6fe5c3f51cd20810ea49"]:
{{{
#!CommitTicketReference repository=""
revision="14c8456ffe7e6388383e6fe5c3f51cd20810ea49"
Fixed #23416 -- Make sure DatabaseCreation respects checks.
Migrations respected Field.db_parameters()['check'], but
DatabaseCreation was still using just Field.db_type().
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23416#comment:4>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.99f6f120482cd0184f83ceae2af03e47%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
