0.6.4-dev member count mismatch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BeBot |
Triaged
|
Low
|
Unassigned |
Bug Description
As of 0.6.4-dev revision 53 various member commands give different results:
Example:
The user table for our bot currently contains a total of 263 rows.
220 are user_level = 2 (member, right?).
1 row is user_level = 2 AND deleted_at <> NULL (so 219 active members, right?).
43 rows are user_level = 0 AND deleted_at <> NULL.
!member
Reply tell states: "218 members in Thefist :: click to view" - top of info box states: "Buddy List Count: 216" - adding up numbers next to professions gives a total of 218.
!member list
Reply tells state: "220 members in Thefist :: click to view (page x of 5)" - number of rows returned matches this (220).
!buddylist
Reply tell states: "216 buddies in Thefist's buddylist :: click to view" - number of rows returned matches this (216).
Changed in bebot: | |
importance: | Undecided → Low |
milestone: | none → 0.6.5 |
status: | New → Triaged |
Oh, and with !member list returning 220 - as well as those expected to be returned - it returns the user who is user_level = 2 but deleted_at <> NULL.