How peculiar... Because according to your list of add-ons in the other thread, you DO have WDB Extra Stats installed. I presumed (wrongly) that the library/ExtraStats files belonged to that.
Whatever the add-on was/is, it looks like you had issues with it before:No, not that one. Refer http://xenforo.com/community/threads/extra-statistics.48833/#post-651103
It's still something to be considered. It, however, creates the opposite problem: the upgrade completes as expected and you then remove the add-on (as in many cases, the conflicts come from add-ons that provide functionality similar to core features). That add-on cleans up its schema changes (as it should) and now you're missing the fields in question. That said, that's something that can theoretically happen right now as well.Is it still on the to-do list for a fix?
I would expect any upgrade making table changes, would first test for the changes already existing before making the change and causing an SQL stop and impacting the remainder of its SQL. But I can see how this can be considered an add-ons cause for not prefixing it's DB changes, but hoping it doesn't result in finger pointing and no action
I've looked closer, and it's an add-on called "User Statistics", with an id of ExtraStats, and version 0.9.1 I've searched threads and resources, but cannot narrow down an add-on by this name. It's disabled on my production server, so I'll uninstall it and check if it removes it's added index to xf_user, so that I don't have the same issue when upgrading production to 1.2How peculiar... Because according to your list of add-ons in the other thread, you DO have WDB Extra Stats installed. I presumed (wrongly) that the library/ExtraStats files belonged to that.