MySQL error, null handling changed on integers??

[Ron]

I am "suddenly" getting an error from MySQL on my server.

Sometime between January 10 and January 15, inserts into a MySQL table are failing.

The code is very simple, as is the table. Here they are:

The insert statement:
$sql = "insert into xxxxxxxxxx values ($rs_1111111111,$rs_2222222222,'')";
Note that the double single-quote for the third column value is hard coded.

The table create:
 CREATE TABLE `xxxxxxxxxxx` (
  `1111111111` mediumint(8) NOT NULL default '0',
  `2222222222` mediumint(8) NOT NULL default '0',
  `XXXXXXXXXX` tinyint(1) default NULL,
  KEY `3333333333` (`3333333333`),
  KEY `4444444444` (`4444444444`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

And the error message I get is pretty straightforward as well:

Incorrect integer value: '' for column 'XXXXXXXXXX' at row 1

It had been working for over a year; hundreds of successful inserts.

Now I understand why this might not be working, but what I want to know is what changed on the server to cause this to suddenly start failing? Has a new version of MySQL been installed in that timeframe? Is there a release notes page for that version that might explain the error? Was the server put into ANSI mode?

Thanks.

[the_ancient]

You may already know this, but

$sql = "insert into xxxxxxxxxx values ($rs_1111111111,$rs_2222222222,'')"; 

should be

$sql = "insert into xxxxxxxxxx values ($rs_1111111111,$rs_2222222222,NULL)"; 

I cant tell you what has changed, I believe there was some updates to PHP that might have effected the mysql drivers......

[Ron]

Yes, I'm sure that's what it should be, and clearly how I should have written it, give or take. Clearly it was not the way I would have written it had I looked at the table defs. I probably copied some code from an old version of phpBB2.x or some hack for it.. I don't recall.

Yes, you are correct, the question I have is -- what changed??

Looking at MySQL docs, it could be the server was put into ANSI mode or strict trans tables or something like that, too. Or maybe it was a MySQL version change. I dunno. But something definitely changed.

I've already coded around it, or more properly in this instance I've corrected my code to be proper to account for this change. But I'm used to doing that here whenever they break something of mine. Or in this case change something that highlights my bad code.

THANKS for offering the suggestion, T_A

[gohighvoltage]

I am willing to bet the server was accidentally changed to Strict mode.


By default, MySQL is enabled with strict_mode ON.

So if they did an upgrade of some kind, this could of caused your issues.

Do you have access to my.ini file?