Details
-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
extension/ezoracle 1.8.2, extension/ezoracle 2.0.2
-
None
Description
The problem lies in the fact that integer columns are created with full precision (ie. 38), and later compared with their base definition - with a precision of 11.
While it would be technically correct to create integers with a precision of 11,
- it is slightly lower in Oracle to do so (the numbers are still stored using the same space, but an extra check is added for bounds overflowing)
- we prefer backwards compat for all existing installations anyway
Attachments
Issue Links
- relates to
-
EZP-15675 Wrong suggestions from database consistency check when using Oracle
- Closed