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

Messages with duplicate timecreated values not displayed

    Details

    • Database:
      MySQL
    • Testing Instructions:
      Hide

      Youll need 2 users.

      Log in as user A and send user B a message.
      Log in as user B and go to messaging.
      Check that you can move back and forth between "recent message" and "all messages". The links are beneath the user's picture above the message history.
      You should not receive any errors and the messages should be ordered correctly. The newest messages should be last, immediately above the new message text box.

      Select "recent conversations" from the messaging navigation drop down and check that that doesn't give any errors.

      For bonus points you can run the attached script and repeat.

      Show
      Youll need 2 users. Log in as user A and send user B a message. Log in as user B and go to messaging. Check that you can move back and forth between "recent message" and "all messages". The links are beneath the user's picture above the message history. You should not receive any errors and the messages should be ordered correctly. The newest messages should be last, immediately above the new message text box. Select "recent conversations" from the messaging navigation drop down and check that that doesn't give any errors. For bonus points you can run the attached script and repeat.
    • Affected Branches:
      MOODLE_21_STABLE
    • Fixed Branches:
      MOODLE_23_STABLE
    • Pull Master Branch:
      MDL-30022_message_duplicate

      Description

      I currently have a scenario where two entries in the mdl_message_read table are from the same user, to the same user, and have an identical timecreated value.

      When viewing "Recent messages", only one of the two messages shows up.

      However, if I edit the "timecreated" database value to a different value, both messages are displayed.

        Gliffy Diagrams

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  10/Sep/12