On 6-Dec-07, at 11:46 AM, Brian Parkinson wrote:
Hello -
Wondering if someone out there has some MySQL experience - running
into
a weird issue, and I'm stumped. This is perhaps not exactly an iBATIS
issue, but I received no response over at the MySQL forums, so it's
worth a shot:
I have a very simple data model working in iBATIS (getting familiar
with
this, and enjoying how it's put together). It works on Windows and Mac
OS X, with MySQL version 5.0.45.
For our deployment, we're using Debian 5.0.32.
When I run my unit tests on the Debian box, I get foreign key
constraint
violations which I do not get on the Windoze or Mac box.
Are they all using the same storage engine (differing defaults)?
InnoDB checks such constraints, other engines generally do not.
--Toby
To wit:
[junit] ------------- Standard Output ---------------
[junit] --- The error occurred in
com/ecobee/foundation/ibatis/SqlMapThermostat.xml.
[junit] --- The error occurred while applying a parameter map.
[junit] --- Check the Thermostat.LocationParameterMap.
[junit] --- Check the statement (update failed).
[junit] --- Cause:
com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException:
Cannot add or update a child row: a foreign key constraint fails
