Using a checkbox was just an example for explanatory purposes.
Setting a value to default of 0 is exactly how I thought I would get around the problem, but it doesn't work... not with fasthosts in the UK anyway.
`b_id` int(11) unsigned NOT NULL AUTO_INCREMENT,
`b_bookingid` int(11) DEFAULT '0' COMMENT 'Copy of b_id for extra person',
They're saying that strict requires an input and they're suggesting I use a hidden field. Well, if this was a record that required admin authorisation before it went live, then all a hacker would need to do is show source, find the hidden field change the records visibility and they could post anything they wanted.
As far as I am aware, it only seems to be happening on INT columns.
So Ray, as far as you're aware, strict should still allow an insert if the column has got a default value applied; is that right? That's not how it's happening though!
I've had to get around it by making sure that my insert behaviour has a value in it for every column whether it is being used or not.