Opened 10 years ago
Closed 10 years ago
#23264 closed Bug (fixed)
db_constraint=False not enforced on migrations
Reported by: | Jay McEntire | Owned by: | Andrew Godwin |
---|---|---|---|
Component: | Migrations | Version: | 1.7-rc-2 |
Severity: | Release blocker | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
When adding db_constraint=False on a ForeignKey or directly on a Migration still causes the constraint to be created.
Change History (4)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Severity: | Normal → Release blocker |
---|---|
Triage Stage: | Unreviewed → Accepted |
Hi,
Indeed, the constraint seems to be created regardless of the db_constraint=False
.
Note that the same bux exists for ManyToManyField.db_constraint
.
I'll bump the ticket to the release blocker
status too.
Thanks.
comment:3 by , 10 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Ah, I didn't even know we had db_constraint! Adding now.
comment:4 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Example...
foo/models.py
foo/migrations/0001_initial.py
/manage.py sqlmigrate foo 0001
FYI - This is using postgres