#34727: Error in CharField with TextChoices and missing max_length parameter
-------------------------------------+-------------------------------------
Reporter: osamahasanone | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 4.2
Severity: Normal | Resolution:
Keywords: test, sqlite, | Triage Stage:
CharField, max_length,choices | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* component: Uncategorized => Testing framework
Comment:
`max_length` is required on databases other than PostgreSQL. I believe the
issue is that system checks (which would highlight this issue) are run
after the test database is created (which fails due to missing
`max_length`). I guess it's common to catch this sort of mistake using
`runserver` before running `test`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34727#comment:1>
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/01070189745d874b-670ca5c7-17f3-4802-9ed1-b503115a5d55-000000%40eu-central-1.amazonses.com.
