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

null event.uuid's discovered when upgrading to Moodle 2.4

    XMLWordPrintable

Details

    • 8
    • BACKEND Sprint 7

    Description

      When I tried to upgrade to Moodle 2.4 from Moodle 2.3.3+, I received the following message:

      System
       
      DDL sql execution error
       
      More information about this error
       
      Debug info: Data truncated for column 'uuid' at row 11
      ALTER TABLE mdl_event MODIFY COLUMN uuid VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '' after visible
      Error code: ddlexecuteerror
      Stack trace:
      line 432 of /lib/dml/moodle_database.php: ddl_change_structure_exception thrown
      line 860 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
      line 88 of /lib/ddl/database_manager.php: call to mysqli_native_moodle_database->change_database_structure()
      line 77 of /lib/ddl/database_manager.php: call to database_manager->execute_sql()
      line 586 of /lib/ddl/database_manager.php: call to database_manager->execute_sql_arr()
      line 598 of /lib/ddl/database_manager.php: call to database_manager->change_field_type()
      line 1308 of /lib/db/upgrade.php: call to database_manager->change_field_precision()
      line 1493 of /lib/upgradelib.php: call to xmldb_main_upgrade()
      line 284 of /admin/index.php: call to upgrade_core()
      

      Attachments

        Activity

          People

            skodak Petr Skoda (Inactive)
            mjfrith Michael J. Frith
            Sam Hemelryk Sam Hemelryk
            Dan Poltawski Dan Poltawski
            Ankit Agarwal Ankit Agarwal
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Clockify

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.