Opened 6 years ago

Last modified 5 weeks ago

#11964 new New feature

Using database-level CHECK CONSTRAINTS

Reported by: schinckel Owned by: nobody
Component: Database layer (models, ORM) Version: 1.1
Severity: Normal Keywords: check contsraint
Cc: dbrgn, esigra Triage Stage: Someday/Maybe
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: no


I mentioned adding database level CHECK CONSTRAINTS in a post on django-developers.

Attached to this ticket is a patch that provides the functionality listed in the first post of this thread. This is not complete: it only allows simple constraints, and is missing a complete test suite.

Attachments (1)

check_constraints.diff (15.8 KB) - added by schinckel 6 years ago.
Contains patches against trunk that enable check constraints

Download all attachments as: .zip

Change History (9)

Changed 6 years ago by schinckel

Contains patches against trunk that enable check constraints

comment:1 Changed 5 years ago by russellm

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Someday/Maybe

If we do this, it should be tied into the model validation framework in some way.

comment:2 Changed 5 years ago by schinckel

Agreed. The initial patch was made before the changes with model validation had hit. I will get back to this at some stage.

comment:3 Changed 4 years ago by julien

  • Severity set to Normal
  • Type set to New feature

comment:4 Changed 3 years ago by aaugustin

  • UI/UX unset

Change UI/UX from NULL to False.

comment:5 Changed 3 years ago by aaugustin

  • Easy pickings unset

Change Easy pickings from NULL to False.

comment:6 Changed 3 years ago by dbrgn

  • Cc dbrgn added

comment:7 Changed 4 months ago by timgraham

  • Patch needs improvement set

comment:8 Changed 5 weeks ago by esigra

  • Cc esigra added
Note: See TracTickets for help on using tickets.
Back to Top