Details
-
Bug
-
Resolution: Obsolete
-
Medium
-
None
-
4.0.7, 4.1.4, 4.2.0
-
None
Description
A lot of longtext fields are defined as having a 'default false' value.
The default value is stripped when generating both mysql and postgres versions of the corresponding sql.
Since no default value is generated, it is safe to assume that at runtime there is no try to insert NULL values into them. It follows that Oracle should be able to do without a default value, too.
But when trying to transform the generic schema version into a localized version, the 'default false' definitions are kept, so that comparing to a localized schema gotten from db is hard.
This means that db schema comparisons always have to be done using not the localized version but the generalized version, and this is bad, as it makes it hard to generate correct update scripts (see linked issue).
Attachments
Issue Links
- relates to
-
EZP-15675 Wrong suggestions from database consistency check when using Oracle
- Closed