Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-6855

Compare one 1.7 clean installation DB with one 1.7 installation migrated from previous version

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.7.2
    • Fix Version/s: 2.0.10
    • Component/s: Installation
    • Labels:
      None
    • Environment:
      MySQL & PG
    • Database:
      MySQL, PostgreSQL
    • Affected Branches:
      MOODLE_17_STABLE
    • Fixed Branches:
      MOODLE_20_STABLE

      Description

      In order to be 100% sure that we haven't forgotten anything with all the new install.xml I would propose to:

      1) Make one clean install of Moodle 1.7
      2) Make one clean install of Moodle, 1.6 and upgrade it up to 1.7
      3) Compare (with phpMyAdmin) that every table/field is exactly equal and that we haven't forgotten anything, annotating all the differences found.

      It can be done in some hours and will allow us to start thinking about to drop all the old .sql files definitively (plus being 100% confident with the new tables).

      Ideally, this should be performed both under MySQL and PostgreSQL, although checking it under the first could be enough... assuming that PG is 100% up-to-date with MySQL. Your decision.

      Marked as blocker. Not sure if this is too much, but I think it's a must.

        Attachments

        1. 1.6-1.7.sql
          152 kB
        2. 17fresh_vs_17upgraded.diff
          149 kB
        3. diff_default.txt
          2 kB
        4. diff_indexes.txt
          3 kB
        5. diff_unsigned.txt
          2 kB
        6. diff.txt
          0.5 kB
        7. diff.txt
          4 kB
        8. diff.txt
          7 kB
        9. diff.txt
          150 kB
        10. infinite_loop.patch
          0.9 kB
        11. pg74dbstructure.zip
          27 kB
        12. udiff
          130 kB

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  9/Jul/12