I wish it was a bug; I reported this in a recent survey but neither the problem was solved (very likely one binary field in a database) nor I was contacted for an explanation.