Uploaded image for project: 'mod-source-record-manager'
  1. mod-source-record-manager
  2. MODSOURMAN-833

Schema differences between MG Bugfest and clean MG deployment: mod-source-record-manager

    XMLWordPrintable

Details

    • 3
    • Folijet Support
    • Morning Glory R2 2022 Bug Fix
    • Lack of testing

    Description

      Overview:

      The mod-source-record-manager schema for MG bugfest has several elements that do not align with a clean MG deployment. The differences are:

      1. jobexecutionid in table job_execution_source_chunks can be NULL in bugfest, but cannot be NULL in new deployment
      2. Bugfest has extra function that is not present in new deployment: update_job_execution_source_chunks_references
      3. Bugfest has extra trigger that is not present in new deployment: update_job_execution_source_chunks_references on table job_execution_source_chunks
      4. Bugfest has extra trigger that is not present in new deployment: set_id_in_jsonb on table job_execution_source_chunks

      I've attached screenshots showing the differences between the 2 schemas.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                VRohach Volodymyr Rohach
                bsharp Bobby Sharp
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases