Issue 18632 - Localization floating point number formats impede inserting into ODBC databases.
Summary: Localization floating point number formats impede inserting into ODBC databases.
Status: CLOSED DUPLICATE of issue 6600
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ocke.janssen
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-25 14:10 UTC by Unknown
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-08-25 14:10:10 UTC 
I create a MyODBC data source and I define a floating point field in the tables.
Then I make a Form with an autopilot. All seems to be right.
But when I introduce data in the float type field OpenOffice.org sends an
incorrect query due to the coma separator of the floats in my localization
format (Spanish).

In one of my tests MySQL receives this:

INSERT INTO `test` ( `floatfield`) VALUES ( 2,39999999999999991e+00)

MySQL interprets two field values: 2 and 39999999999999991e+00, because of the
',' that in Spanish is the correct separator.

This would be correct:

INSERT INTO `test` ( `floatfield`) VALUES ( '2,39999999999999991e+00')
Comment 1 Frank Schönheit 2003-08-26 08:18:42 UTC 
ocke, is this a resurrection of MySQL's locale problem?
Comment 2 ocke.janssen 2003-08-26 08:27:55 UTC 
.

*** This issue has been marked as a duplicate of 6600 ***
Comment 3 hans_werner67 2004-02-02 12:58:25 UTC 
change subcomponent to 'none'
Comment 4 ocke.janssen 2004-02-10 14:38:42 UTC 
close it