#16694: The test suite no longer runs under Oracle since r16678
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Database layer
Version: 1.3 | (models, ORM)
Resolution: | Severity: Release blocker
Triage Stage: Accepted | Keywords:
Needs documentation: 0 | Has patch: 0
Patch needs improvement: 0 | Needs tests: 0
UI/UX: 0 | Easy pickings: 0
-------------------------------------+-------------------------------------
Changes (by mtredinnick):
* stage: Unreviewed => Accepted
Comment:
*sigh* Anytime anybody claims Oracle supports SQL, people should feel free
to laugh at them. Their NULL handling has been broken forever, in multiple
places, and continues to hurt people (like us) trying to write portable
SQL. This particular issue is because incorrectly Oracle compares NULL and
"" to be equal and the Django backend tries to make things behave
uniformly with respect to that.
It would be nice to avoid having to omit that test entirely (since
null=True is entirely incorrect when written on a model pk field), but
that means checking for explicit null=True versus when Oracle backend adds
it implicitly. Alternative is to skip the test for the Oracle backend
(which hurts in the multi-db case, I suspect).
--
Ticket URL: <https://code.djangoproject.com/ticket/16694#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
