#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 Mariusz Felisiak):
Replying to [comment:3 karosis88]:
> Does it really solve the problem?
Yes.
> 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.
There is no way to switch between databases without changing anything.
It's recommended to use the same database in development and production
environments, unless you're aware of all migration caveats. We accepted
#14094, because `CharField` and `TextField` use different datatypes on
PostgreSQL.
--
Ticket URL: <https://code.djangoproject.com/ticket/34887#comment:4>
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/0107018af9cd4f48-2ef421d7-5370-4f45-b88e-c7535d892522-000000%40eu-central-1.amazonses.com.
