Upgraded MySQL 5.0 Linux -> MySQL 5.1 Windows and now query doesn’t work
Posted by:
Cam Bevis
Date: July 15, 2010 11:00AM
First of all, I know this SHOULDN'T work. We're using a very old DAL/ORM (Pear/DB/GenericDao based) layer that incorrectly surmises that id is not an autoincrement/integer field.
**This statement DOES work in 5.0 Linux, DOES NOT work in 5.1 Windows.** Is there a setting that could be different in my ini (ignore_type_errors="yes":))? I really don't want to add rewriting/upgrading this DAL/ORM (which predates me at the company) to the server upgrade tasks.
Statement
INSERT INTO Party SET partyTypeID = 'PERSON',id = '',comment = '';
Error
Error Code: 1366
Incorrect integer value: '' for column 'id' at row 1)
DDL for Table
CREATE TABLE `Party` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`partyTypeID` varchar(32) NOT NULL DEFAULT '',
`comment` varchar(255) NOT NULL DEFAULT '',
PRIMARY KEY (`id`),
KEY `partyTypeID` (`partyTypeID`)
) ENGINE=MyISAM AUTO_INCREMENT=1017793 DEFAULT CHARSET=latin1;
Subject
Views
Written By
Posted
Upgraded MySQL 5.0 Linux -> MySQL 5.1 Windows and now query doesn’t work
3190
July 15, 2010 11:00AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.