Hi,
for me the problem turned to be that the vendor didn't have a ver 3 ODBC
driver (which J odbc scripts are set up for). There's a beta version of it
available, but I haven't got around to giving it another try yet.
Thanks go to Bill Lam for restoring my sanity through helping me interpret
Bill,
Thank you very much for your response.
Myodbc was too buggy for real-life use the last time I checked a few years
ago, and browsing its support forum suggested the odbc driver was
un-maintained. Has it been improved?
I do not know if the quality of MyODBC has improved. I've never used
Chris,
I included a fragment from odbc.ijs for your reference. As you can see
date and time (91 92?) are not supported. Furthermore blob data type (eg.
_1 and _4) will never be supported in ddfch, as it is impossible to
allocate (2G or more)*rowsize of memory buffer for each blob column.
NB.
On Fri, Sep 24, 2010 at 10:33 AM, bill lam bbill@gmail.com wrote:
I included a fragment from odbc.ijs for your reference. As you can see
date and time (91 92?) are not supported. Furthermore blob data type (eg.
_1 and _4) will never be supported in ddfch, as it is impossible to
allocate
Bill,
Thanks again.
Very helpful and educational.
I now notice that another post previously addressed similar issues
(unsupported data types).
http://jsoftware.com/pipermail/programming/2010-September/020273.html
Perhaps it would save you a little explanation time in the future if
something
Problem summary: J-ODBC access to MySQL DB failing
Environment: Windows XP Pro SP 3(32bit) , Dell 1710 Core Duo, 2GB RAM,
32bit J602a/2008-03-03/16:45, Library 6.02.051, 32 bit MySQL 4.0.1
Overview:
1) Trying to use J ODBC to read a MySQL DB (62 tables, 6000 records
in most populous table). This
