#23073: Oracle 11.2.0.1: Number columns (incl. Booleans) defined with default
break
introspection
--------------------------------------+------------------------------------
Reporter: shai | Owner: shai
Type: Cleanup/optimization | Status: closed
Component: Migrations | Version: 1.7-rc-1
Severity: Normal | Resolution: wontfix
Keywords: oracle | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by shaib):
* status: new => closed
* resolution: => wontfix
Comment:
I tried.
By my understanding now, and also by
[http://stackoverflow.com/questions/8481532/how-do-i-remove-the-default-
value-from-a-column-in-oracle this] !StackOverflow question (second
answer), the only way to really fix this is to use a Sqlite-backend-style
table-recreation for adding columns. With all due respect to Continuous
Integration, we are not going to do '''that''' to work around an Oracle
bug that has already been fixed.
I'm going to just disable the failing test on the specific Oracle server
version.
--
Ticket URL: <https://code.djangoproject.com/ticket/23073#comment:3>
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.08d5ed1ace1742eb6cfd0c6bce201560%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
