This occurs because of a bug in versions of MySQL between 5.0.2 and 5.0.88.
Originally Posted by
http://dev.mysql.com/doc/relnotes/mysql/5.0/en/news-5-0-88.html
Failure to treat BIT values as unsigned could lead to unpredictable results. (Bug #42803)
MySQL was returning values of data-type BIT as BIN values between 5.0.2 and 5.0.88 due to a change in 5.0.2 which allowed storing the binary values (0s and 1s) directly in BIT fields (a bit being 0 or 1). This ended up causing many regressions editing and displaying, and after arguing for many versions that it wasn't a bug, in 5.0.88 they changed the return value to UNSIGNED.
I'm guessing your MySQL version falls between those versions, so your server is returning BIN, which leads since PHP to acknowledge it as a string rather than a number.
This means instead of bitfield = 1, we have bitfield = [GARBAGE]
So VaultWiki is unable to determine if the current page-text has been compressed or not.
Since VaultWiki is supposed to have much laxer requirements for MySQL, I am working on a fix now, but it requires modifications to our database abstract, and everywhere these bit values are used. It may take a few hours before I can apply it everywhere on your install.