#34887: Allow unlimited CharField for SQLite backend
-------------------------------------+-------------------------------------
Reporter: Kar Petrosyan | Owner: Kar
| Petrosyan
Type: New feature | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: SQLite | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
For the record I've opted into accepting this feature in
ticket:35759#comment:6 as to me the situation on SQLite is similar to
Postgres.
On SQLite both `varchar` and `text` are an alias for the same internal
type but it's also the case on Postgres where
[https://www.depesz.com/2010/03/02/charx-vs-varcharx-vs-varchar-vs-text/
they are aliases] for `varlena`).
The lack of constraint enforcement on SQLite is a distinct problem (see
#21471) that allowing `max_length=None` could help solving by providing a
way to restore the previous behaviour for users that need it.
--
Ticket URL: <https://code.djangoproject.com/ticket/34887#comment:5>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070191ebd69d21-ccf0287c-ce08-4053-92ca-ace97fe00e89-000000%40eu-central-1.amazonses.com.
