#34727: Error in CharField with TextChoices and missing max_length parameter
-------------------------------------+-------------------------------------
Reporter: osamahasanone | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: 4.2
Severity: Normal | Resolution: invalid
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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:6 Tim Graham]:
> Offhand, I can't think of a reason why the test runner
couldn't/shouldn't run checks before creating the test database. That
would catch this and improve other situations where time is wasted on
database setup only to fail at the check stage. Thoughts?
Unfortunately, a database is required for some checks because database
features can only be confirmed by introspecting the database, e.g.
[https://github.com/django/django/blob/addbc90049083f1d5f7ac138ed00111b71a75233/django/db/backends/sqlite3/features.py#L149-L159
supports_json_field] on SQLite.
--
Ticket URL: <https://code.djangoproject.com/ticket/34727#comment:7>
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/01070189767f5baf-e8b88f43-8c79-48cf-a498-25b0c30ab095-000000%40eu-central-1.amazonses.com.
