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
col
On Fri, Sep 24, 2010 at 10:33 AM, bill lam 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 (2G or more)*rows
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. 3
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?
If it crashed during ddcol there might be an issue in the catalog
field in column definitions that driver returned. You
