Comment on A Bad Privacy BugComments−vlucas14yMan, the more I see and experience things like this in MySQL, the more impressed (horrified?) I am at how it ever became popular. So glad I've made the switch to Postgres.−ars14yThis isn't really a MySQL issue though. He used bin instead of int, and MySQL did exactly what he asked - stored the raw binary data as is.−drivebyacct214yWhy are rows with 'y' in them being returned when he asked for that value equal to zero?−ars14yNo idea. I would expect it to convert the 0 to a binary format (since that's the format of the column) but it's not.It does raise warning 1292: Truncated incorrect DOUBLE value: 'y ' 1292: Truncated incorrect DOUBLE value: 'y ' (Yes, twice.)Which makes no sense to me.
Comments
Man, the more I see and experience things like this in MySQL, the more impressed (horrified?) I am at how it ever became popular. So glad I've made the switch to Postgres.
This isn't really a MySQL issue though. He used bin instead of int, and MySQL did exactly what he asked - stored the raw binary data as is.
Why are rows with 'y' in them being returned when he asked for that value equal to zero?
No idea. I would expect it to convert the 0 to a binary format (since that's the format of the column) but it's not.
It does raise warning
(Yes, twice.)Which makes no sense to me.