Opened 10 years ago
Closed 10 years ago
#26441 closed Cleanup/optimization (fixed)
Add model Field.db_check() method
| Reported by: | Markus Holtermann | Owned by: | Markus Holtermann |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Model fields have a db_type() method that returns the underlying data type, especially interesting for relational field. The db_parameters() method currently calls db_type() but has a kind of hard coded implementation to get check constraints.
A proper fix for this issue implements a separate db_check() method and allows to call that on its own.
Change History (3)
comment:1 by , 10 years ago
| Has patch: | set |
|---|---|
| Patch needs improvement: | set |
| Summary: | Add dedicated db_check method along db_type → Add model Field.db_check() method |
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 10 years ago
| Patch needs improvement: | unset |
|---|---|
| Triage Stage: | Accepted → Ready for checkin |
comment:3 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
In 103d4e1d: