Oracle 18.104.22.168: Number columns (incl. Booleans) defined with default break introspection
|Reported by:||shai||Owned by:||shai|
|Cc:||timo, andrewgodwin||Triage Stage:||Accepted|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
It seems that on this specific version of Oracle server, if you define a number column with a default, it gets precision 0. This, in turn, means it will be introspected as an IntegerField, even if it was a BooleanField or a BigIntegerField to begin with.
I am not quite sure yet about this description, but that seems to be what I get from tests.
I suspect this can be worked-around by changing the alter-column command which removes the default to also redefine the type. I am not sure supporting one specific, superseded, Oracle version, is worth the hassle. The point going for it is that this is the (Oracle 11) version one can download from Oracle for free, and so this is the version we are trying to use for our CI (and others may want to do the same).
Change History (5)
comment:1 Changed 10 months ago by timo
- Triage Stage changed from Unreviewed to Accepted
- Type changed from Uncategorized to Cleanup/optimization
- Version changed from master to 1.7-rc-1