I have a mysql database with a `TINYINT(4)` column that previously had no value set to default, and I assume `null` was being set as the default value. I had to manually push '0' into the database saving logic every time in my code, so I have now updated the column to instead have an explicit default value of '0'. Now when I save my data, instead `null` is being set, and throwing off my code. When I set `not null` for the column, then it throws an error due to my not passing in a value in my database saving code. I've checked all of my other entries in the table, and do not see any other 'null' values that may be throwing this off - all are either '0' or '1'.

There must be some quirk here with my database. I have the same exact column with the same logic and that is saving as '0' perfectly fine. Looking for any insight into what could be causing this.