Wait... seriously? No wait—seriously???

1. be me
2. bind 1733272193019267 using sqlite3_bind_int64 to an INTEGER column
3. sqlite3_step
sqlite error 778 disk I/O error

1. be me
2. bind 54992003 the exact same way
3. sqlite3_step
no error

18446744073709551615 is the biggest integer that will fit into 8 bytes! That's 10,642 times bigger than what I'm trying to insert. Even if I'm limited to signed 8 byte integers, 9223372036854775808 is the max, and 1733272193019267 is 5,000 times smaller than that. So there can't be an error here. It can't possibly fail to save the number 1733272193019267. How is it failing, then? Did they do something so idiotic as to use some of the high bits of those 8 bytes for vital database consistency state? There's no disk I/O error. This should never happen! #wtf