#34887: Allow unlimited CharField for SQLite backend
-------------------------------------+-------------------------------------
Reporter: karosis88 | Owner: karosis88
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 karosis88):
Replying to [comment:2 Mariusz Felisiak]:
> SQLite has limited number of datatypes, and there is no difference
between `TEXT` and `VARCHAR` (no declared max length), both would be
stored in the `TEXT` datatype. You can use `TextField` for unlimited
`CharField`.
Does it really solve the problem? I want to use CharField and not
TextField (when using sqlite3 for the startup but planning to migrate to
another DBMS).
In such cases, I can use CharField (max_length = 1), but it wouldn't make
any sense for the reviewer.
--
Ticket URL: <https://code.djangoproject.com/ticket/34887#comment:3>
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/0107018af9b95fa5-308c48cd-dc2e-47fc-97ed-1ee604644fdd-000000%40eu-central-1.amazonses.com.
