#27676 closed New feature (fixed)
MariaDB 10.2 supports defaults for text columns
Reported by: | Adam Johnson | Owned by: | Adam Johnson |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | me@… | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Django has workaround code for MySQL's deficiency not supporting DEFAULT for TEXT, BLOB, and JSON columns, but MariaDB 10.2 fixes this ( see https://mariadb.com/kb/en/mariadb/what-is-mariadb-102/: "BLOB and TEXT fields can now have a DEFAULT value." ).
Django should allow DEFAULT for these columns when on MariaDB 10.2+.
Change History (7)
comment:1 Changed 6 years ago by
Triage Stage: | Unreviewed → Someday/Maybe |
---|---|
Type: | Bug → New feature |
comment:4 Changed 5 years ago by
Patch needs improvement: | set |
---|---|
Triage Stage: | Ready for checkin → Accepted |
On the PR, Adam said, "I was thinking of forming a better plan around MariaDB first."
comment:5 Changed 3 years ago by
Django 3.0 will officially support MariaDB 10.1+. I think it's time to change this feature flag. Adam, can you resubmit your patch?
comment:6 Changed 3 years ago by
Patch needs improvement: | unset |
---|
First some consensus is needed about whether Django should officially support MariaDB.