MySQL Bugs: #43574: insert and update error with decimal data type in Entity Framework

Bug #43574	insert and update error with decimal data type in Entity Framework
Submitted:	11 Mar 2009 22:55	Modified:	3 Apr 2009 15:10
Reporter:	Andreas Winkler
Status:	Closed
Category:	Connector/Net	Severity:	S1 (Critical)
Version:	6.0.0.0	OS:	Microsoft Windows
Assigned to:		Target Version:
Tags:	entity framework, provider

Description:
If you use a culture - for eample german - in your system environment the update and
insert command (with decimal data types for example) generated by the tokenizer throws
the exception 'column count doesn't match value count at row 1'.

If the value to store in a decimal field is 0, the command will be executed
successfully.

I guess, the error is caused by the different number formats for decimal,float etc. in
german.

Thanks,

Andreas

How to repeat:
DROP TABLE IF EXISTS `sc`.`kundenauftrag`;
CREATE TABLE  `sc`.`kundenauftrag` (
  `AuftragsNr` int(11) NOT NULL AUTO_INCREMENT,
  `KundenNr` int(11) NOT NULL DEFAULT 0,
  `Rechnungswert` decimal(19,2) NOT NULL DEFAULT '0.00',
  `Position` int(11) NOT NULL DEFAULT '1',
  PRIMARY KEY (`AuftragsNr`,`Position`) USING BTREE,
  KEY `KundenNr` (`KundenNr`)
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=latin1 COLLATE=latin1_german1_ci;

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/70980

fixed in 6.0.1

An entry was added to the 6.0.1 changelog:

An insert and update error was generated by the decimal data type in the Entity
Framework, when a German collation was used.

This bug still exists for me. I'm from Denmark, and I'm currently using utf-8 on the
database. Why not simply replace all numerical commas with dots when building the sql?

This bug still exists for me. I'm from Spain, with DECIMAL data type the connector work
fine, but with DOUBLE data type the connector 
throws the exception 'column count doesn't match value count at row 1'.

Due to server being down I can not check on patch and confirm Bug#44455 is actually
regression but it might be.