Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-3818

SQL patch scripts are missing exact version number in distribution

    Details

      Description

      Problem:

      The SQL patch scripts for enterprise versions are missing the exact version numbers where they should be applied. Instead they are all concatenated into a single big file '<version>_patch.sql' for each minor version.

      AT:

      • We do not lose the version numbers for the sql patch scripts.
      • SQL upgrade tests, instance-migration still work

        Issue Links

          Activity

          Hide
          gimbel Robert Gimbel added a comment -

          Discussion results:

          • upgrade scripts are always independent from patch scripts
          • it is documented in minor version and patch level upgrade guide which patch scripts exist (including reference to ticket and info which index is created)
          • developer guide contains the following info
            • patch scripts are never part of upgrade
            • create scripts and drops scripts are adjusted
          Show
          gimbel Robert Gimbel added a comment - Discussion results: upgrade scripts are always independent from patch scripts it is documented in minor version and patch level upgrade guide which patch scripts exist (including reference to ticket and info which index is created) developer guide contains the following info patch scripts are never part of upgrade create scripts and drops scripts are adjusted
          Show
          lipphardt Christian Lipphardt added a comment - See https://app.camunda.com/confluence/display/camBPM/SQL+Patch+Scripts
          Hide
          gimbel Robert Gimbel added a comment -

          Why did you use confluence for the developer guide?

          Shouldnt we use this one here in the docs: http://docs.camunda.org/latest/guides/developer-guide/

          ?

          Show
          gimbel Robert Gimbel added a comment - Why did you use confluence for the developer guide? Shouldnt we use this one here in the docs: http://docs.camunda.org/latest/guides/developer-guide/ ?
          Hide
          maintenance@camunda.com Maintenance added a comment -

          When I talked about developers I meant our core developers so they know
          which files to add/modify in case we have to provide another patch script.
          No public audience.

          Show
          maintenance@camunda.com Maintenance added a comment - When I talked about developers I meant our core developers so they know which files to add/modify in case we have to provide another patch script. No public audience.
          Hide
          gimbel Robert Gimbel added a comment -

          I think that is what the developer guide is for. From my side it is ok to put it in there

          Show
          gimbel Robert Gimbel added a comment - I think that is what the developer guide is for. From my side it is ok to put it in there
          Hide
          lipphardt Christian Lipphardt added a comment -

          Alright, I'll transfer it.

          Show
          lipphardt Christian Lipphardt added a comment - Alright, I'll transfer it.
          Hide
          gimbel Robert Gimbel added a comment -

          great thanks

          Show
          gimbel Robert Gimbel added a comment - great thanks
          Hide
          lipphardt Christian Lipphardt added a comment -

          I added an assembly to zip / tar the sql-scripts up additionally

          Show
          lipphardt Christian Lipphardt added a comment - I added an assembly to zip / tar the sql-scripts up additionally
          Hide
          sebastian.menski Sebastian Menski added a comment -

          Cool thanks.

          Show
          sebastian.menski Sebastian Menski added a comment - Cool thanks.

            People

            • Assignee:
              matthijs.burke Matthijs Burke
              Reporter:
              lipphardt Christian Lipphardt
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development