Red Hat Bugzilla – Bug 84872
[patch] MyODBC wants to use "." as decimal point when talking to MySQL, but does not set numeric locale correctly
Last modified: 2013-07-02 22:59:45 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030206
Description of problem:
it is possible to create new tables
but it ends everytime with different sql-syntax-errors while "create new
"update" works sometimes
the "privileges" are correct:
open a sql-statement window
type the correct statements without ending ";"
there are absolutely no problems!
insert into tab_1 values ("1","test1")
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a new table (gui)
2. try to insert a new record
3. update an existing record
Actual Results: [unixODBC][TCX][MyODBC]Column count doesnï¿½t match
value count at row 1
Expected Results: all should work
caolanm->shrek-m: Is this still the case with a contemporary
$ cat /etc/fedora-release
Fedora Core release 3 (Heidelberg)
$ rpm -q openoffice.org unixODBC mysql mysql-server
- create a new userDSN with
- create a new dadasource (MySQL or ODBC)
- create a new table (without primary key)
OOo will create a primary key
- insert data
for each new row i have to close the connection
"Fehler beim EinfÃ¼gen des neuen Datensatzes
[unixODBC][TCX\MyODBC] You have an error in your SQL syntax near
00000000000e+01' at line 1"
- changing existing entries is possible
LANG=C oowriter /*all is OK*/
LANG=de_DE oowriter /*"ERROR*/
$ env | grep LANG
it seems that the LANG is the problem
Argh!, I found it. A problem with setlocale in MyODBC.
Created attachment 107765 [details]
patch to fix MyODBC
setlocale(LC_NUMERIC,"English") -> setlocale(LC_NUMERIC,"C");
My, that's ugly :-( ... will fix. Thanks for the detective work!
Caolan, how far back are we supporting OpenOffice? I'm wondering
which releases I need to put this fix into ...
Each OOo update we do we push simultaneously for FC2/FC3/RHEl-4/rawhide
I've pushed this fix into fc2, fc3, and rawhide, but it's too late for
RHEL4 :-( ... it'll have to go into U1.
I'll leave the bug report open to remind me to do that when the U1
Adjust bz entry to mention RHEL4.
Just for completeness, this problem was reported to MySQL some time ago, and only partially fixed:
i do not now if it is fixed, i do not use rhel.
please close it, i have no permission.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.