#22816: Oracle test failure: Inspecting NullBooleanField
-------------------------------------+-------------------------------------
Reporter: shai | Owner: shai
Type: Bug | Status: new
Component: Database layer | Version:
(models, ORM) | 1.7-beta-2
Severity: Release blocker | Resolution:
Keywords: oracle | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by shai):
This was introduced by a03d38ddd43957a402b64caddf74a73df72140fb and
5c95a55330bc2531405700a399bfb555bfe80120 on master
(342b25449d800ce29ae56ff8285869cbc3133a75 and
1238f92c649ccd4ba99da0ce70be7597c90515d4 on stable/1.7.x). The first
commit in each pair introduces a `can_introspect_null` database-feature,
and sets it to False for Oracle; the latter uses the flag in tests for
integer and boolean fields.
Oracle has issues introspecting nullability in character fields, because
it `interprets_empty_strings_as_nulls` (so the backend defines all
character fields as nullable in order to allow empty strings); but it has
no such issues with integer fields or boolean fields.
Unless the `can_introspect_null` flag serves some 3rd-party backend, I
suggest that we simply revert these four commits.
--
Ticket URL: <https://code.djangoproject.com/ticket/22816#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.7fddc866cc1f94cff09dbd21db876054%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
