Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-15697

bad definition of longtext fields in db_schema.dba

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Medium Medium
    • None
    • 4.0.7, 4.1.4, 4.2.0
    • Database related
    • 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

        Activity

          People

            unknown unknown
            72f8acac-185f-4a54-9470-a7473f50daab@accounts.ibexa.co Gaetano Giunta
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: