Issue 32862 - Buggy ODBC Access to MySQL
Summary: Buggy ODBC Access to MySQL
Status: CLOSED WONT_FIX
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P2 Trivial (vote)
Target Milestone: ---
Assignee: christoph.lukasiak
QA Contact: issues@dba
URL: http://www.oooforum.org/forum/viewtop...
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-11 21:05 UTC by msowka
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 msowka 2004-08-11 21:05:22 UTC 
Note You can read another description of the symptoms in the URL provided.

The 101:
- I've installed unixODBC + MySQL and manged to add my DB as a Data Source in OO
- when accessing tables with bigint column types I would get:

Message Box: "The data conents could not be updated",
"[unixODBC][TCX][MyODBC]You have an error in your SQL syntax near " at line 1"

Clicking more I get:

-Error
-SQL Status: 42000
-Error code: 1064 

After modifying the table by changing the column type from bigint to Integer I
managed to get it to work.

I'm not sure what other info I can provide...

Mike
Comment 1 christoph.lukasiak 2004-09-15 09:57:30 UTC 
mine
Comment 2 christoph.lukasiak 2004-09-15 10:06:50 UTC 
clu->msowka: this is a driver problem - it works fine for me (bigint), so in
principle it works (from oo side) - this do not solve your problem, but we
cannot fit oo to single driver (the problem is, that a lot of driver do not use
the standards properly) 

p.s. try an other driver (if you need this format) - an other possiblity that
can help is to register your data source in oo under data type: mysql insted of
odbc (if you do not have done it already;)
Comment 3 christoph.lukasiak 2004-09-15 10:07:19 UTC 
close