Bug with handling of bool and false as default value

[johnbrett]

I have the following table:

When queried in the following way, it seems not to register the "false"'s that were created as a default value, only the one I manually set to false:

It's as if the values set to false as a default value...aren't really false?

[johnbrett]

After running:

UPDATE jobs
SET verified = false
WHERE verified IS NOT TRUE;

I now get the correct number of rows... but what is this fake false that exists ?

[awalias]

Very strange, John. Do the fake falses persist when you refresh the dashboard?