<![CDATA[11.7 VST stats bug fix]]>Rich's presentation on what's new in 11.7 contained this tidbit, with reference to _*stat:
"OE 11.7.0 fixed VSI for base != 1"

Rereading that presentation recently, I'm wondering how much of my VST code is now broken. I didn't know until 2017 that that behaviour was a bug. Just wondering aloud; I'm not expecting anyone else to answer that. 😉

For example:
proserve sports -basetable -1 -tablerangesize 4
find _tablestat where _tablestat-id = -1.
display _tablestat-id.

11.6 (and below) result:
** _TableStat record not on file. (138)

11.7 result:
-1

Just curious whether PT will need to change to deal with that in 11.7+.

]]>https://community.wss.com/topic/13/11-7-vst-stats-bug-fixRSS for NodeWed, 12 Aug 2026 00:21:19 GMTWed, 14 Mar 2018 20:46:50 GMT60<![CDATA[Reply to 11.7 VST stats bug fix on Wed, 14 Mar 2018 23:31:10 GMT]]>Except for a few weirdos base = 1 is kind of the norm 😉

(I do understand your use case -- I do that too although probably less often than you seem to. But it is helpful to verify that ProTop is behaving as expected.)

]]>https://community.wss.com/post/51https://community.wss.com/post/51Wed, 14 Mar 2018 23:31:10 GMT<![CDATA[Reply to 11.7 VST stats bug fix on Wed, 14 Mar 2018 23:28:24 GMT]]>I'm not a big fan of limiting the _user*stats. I sort of understand why they did it but I'm not terribly anxious to see anyone use it.

]]>https://community.wss.com/post/50https://community.wss.com/post/50Wed, 14 Mar 2018 23:28:24 GMT<![CDATA[Reply to 11.7 VST stats bug fix on Wed, 14 Mar 2018 20:54:00 GMT]]>In a similar vein (though this is a new feature, not a bug fix), we have new stats params:

baseusertable
baseuserindex
usertablerangesize
userindexrangesize

I haven't played with these yet, or even thought about them too much. Just curious if anyone else has.

]]>https://community.wss.com/post/47https://community.wss.com/post/47Wed, 14 Mar 2018 20:54:00 GMT