Uploaded image for project: 'phpBB3'
  1. phpBB3
  2. PHPBB3-13033

Duplicate entry SQL error thrown when running notifications_use_full_name migration

    Details

    • Type: Bug
    • Status: Unverified Fix
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.1.0-dev
    • Fix Version/s: 3.1.0-RC5
    • Component/s: Update system
    • Labels:
      None

      Description

      When running the notifications_use_full_name.php migration, the following error is thrown:

      Duplicate entry 'notification.type.approve_post' for key 'type' [1062]
       SQL
       UPDATE phpbb_notification_types SET notification_type_name = 'notification.type.approve_post' WHERE notification_type_name = 'approve_post'
      

        Issue Links

          Activity

          Hide
          nickvergessen Joas Schilling added a comment -

          This happens if the code is updated and a notification is triggered, before the database has been updated.

          Show
          nickvergessen Joas Schilling added a comment - This happens if the code is updated and a notification is triggered, before the database has been updated.
          Hide
          nicofuma nicofuma added a comment - - edited

          For me disabling the board should be the first step of the update process, so this issue is more like a won't fix.

          Show
          nicofuma nicofuma added a comment - - edited For me disabling the board should be the first step of the update process, so this issue is more like a won't fix.
          Hide
          Senky Senky added a comment - - edited

          nicofuma is right. You can't expect board to work updating files, but not database.

          btw, is this the only ticket blocking 3.1-RC4 release?

          Show
          Senky Senky added a comment - - edited nicofuma is right. You can't expect board to work updating files, but not database. btw, is this the only ticket blocking 3.1-RC4 release?
          Hide
          naderman Nils Adermann added a comment -

          While I think it's fine for errors to be thrown in such a case, we should avoid creating situations which entirely break further updates, so i do think we should fix this.

          Show
          naderman Nils Adermann added a comment - While I think it's fine for errors to be thrown in such a case, we should avoid creating situations which entirely break further updates, so i do think we should fix this.

            People

            • Assignee:
              nickvergessen Joas Schilling
              Reporter:
              prototech prototech
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development