Still running 3.5.4
Was contacted by a user who said the system was showing he had 65534 unread PMs when as far as he could tell he didn't have any. I went into the 'user' table via phpMyAdmin and reset his 'pmunread' value to 0.
While there, I did a search for other users with pmunread values >= 1000 (we limit storage to 100 pms) and found several others. All were values 65532-65534.
pmunread is an unsigned smallint, with range therefore of 0-65535, so these look to be values that had been reduced to one or more below zero, thus "rolling over" to the high 65k numbers.
Only thing I can postulate is that they had some unread PMs that they deleted without reading, and that somehow this caused a "double dip" and reduced the count two-for-one. But I tried testing this theory, and deleting unread PMs only reduced the count 1 for each message.
Can anybody provide insight what could cause the unread pm number to get reduced below zero?
Was contacted by a user who said the system was showing he had 65534 unread PMs when as far as he could tell he didn't have any. I went into the 'user' table via phpMyAdmin and reset his 'pmunread' value to 0.
While there, I did a search for other users with pmunread values >= 1000 (we limit storage to 100 pms) and found several others. All were values 65532-65534.
pmunread is an unsigned smallint, with range therefore of 0-65535, so these look to be values that had been reduced to one or more below zero, thus "rolling over" to the high 65k numbers.
Only thing I can postulate is that they had some unread PMs that they deleted without reading, and that somehow this caused a "double dip" and reduced the count two-for-one. But I tried testing this theory, and deleting unread PMs only reduced the count 1 for each message.
Can anybody provide insight what could cause the unread pm number to get reduced below zero?
Comment