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

mod_data: Simultaneously added entries do not sort correctly

XMLWordPrintable

    • MOODLE_27_STABLE
    • MOODLE_27_STABLE
    • mdl45232
    • Hide
      1. Create a database activity
      2. Add a text field to the activity field defintions (call it 'name')
      3. Go to the 'templates' pane and save the 'list template'
      4. Add 3 entries in this database in the following order: 'one', 'two', 'three'
      5. In your database, you need to set all those entires to have the same timemodified time. If you've got many records in your database your gonna need to workout what database activity it is and which entries you are modifiying. Dan was lazy when writing these testing instructions and just did the easy thing updating all records:

        UPDATE mdl_data_records SET timemodified = '1398324167';
        

      6. Go to the list view of the database activity amd at the bottom, set the 'Sort by' to 'Time modified' and switch between ascended and descending.
      7. VERIFY: that the order changes when you switch between ascending and descending
      Show
      Create a database activity Add a text field to the activity field defintions (call it 'name') Go to the 'templates' pane and save the 'list template' Add 3 entries in this database in the following order: 'one', 'two', 'three' In your database, you need to set all those entires to have the same timemodified time. If you've got many records in your database your gonna need to workout what database activity it is and which entries you are modifiying. Dan was lazy when writing these testing instructions and just did the easy thing updating all records: UPDATE mdl_data_records SET timemodified = '1398324167'; Go to the list view of the database activity amd at the bottom, set the 'Sort by' to 'Time modified' and switch between ascended and descending. VERIFY: that the order changes when you switch between ascending and descending

      When two entries are added to a database in the same second, they do not sort as expected. This causes behat to fail on fast enough machines.

      Simple change to have the last-resort id sort follow the requested ordering; this ensures when sorting by timecreated/modified that entries are strictly ordered, satisfying behat.

            tlevi Tony Levi
            tlevi Tony Levi
            Dan Poltawski Dan Poltawski
            Sam Hemelryk Sam Hemelryk
            John Okely John Okely
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

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