To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102791 Issue #|102791 Summary|ODBC binds NUMERIC and DECIMAL statement parameters as | CHAR Component|Database access Version|OOO310m11 Platform|PC URL| OS/Version|Windows XP Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|none Assigned to|dbaneedsconfirm Reported by|ludob
------- Additional comments from lu...@openoffice.org Mon Jun 15 12:16:58 +0000 2009 ------- ODBC binds NUMERIC and DECIMAL statement parameters as CHAR. As a result the values are quoted as any other string. This is fine for databases such as Oracle and MySQL that cast automatically a string to numeric or decimal. DB2 however does not allow a string to decimal assignment. Updating or inserting decimal values is not working and throws the database error SQLSTATE=42821 SQLCODE=-408. OPreparedStatement::setObjectWithInfo() forces DataType::DECIMAL and DataType::NUMERIC to bind as a string (setString(parameterIndex,aValue);). I suppose this was not done by accident. What is the reason for this? OTools::getBindTypes does generate the correct bindtypes for DataType::DECIMAL and DataType::NUMERIC but they are not used. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org