Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries, Event 9 IIS log failed to write entry, wwwxxx jeffs, Catastrophic failure Unexpected method call sequence. 0x8000ffff (-2147418113)., ksh lock a file, [unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed, sed: -e expression #1, char 1: unterminated address regex, procmail + change subject, w2ksp4.exe download, /proc/kallsyms format



#1: column display widths reported incorrectly, columns truncated on

Posted on 2010-03-10 23:04:45 by Brandon Valentine


I'm trying to use MyODBC to connect the UPS Worldship 2010 desktop
application to a MySQL 5.1.44 server. I am able to connect to the
server just fine, but when browsing the database the column display
widths show up incorrectly. For instance, a column defined in MySQL
as an int(11) shows up as an int(4). In fact, all integer columns
seem to be showing up as int(4). When the Worldship app tries to
insert into a table through MyODBC it appears to be truncating the
fields to the display width being reported for that column. The
inserts are failing because I have a foreign key constraint on one of
the columns that catches the truncated ID and doesn't permit the
insert. What I would like is to understand why the MyODBC driver is
misreporting the column widths and what might be done to present the
correct column widths to the application. I have tried the same
operation using MyODBC 3.51.27 as well as and both have the
same problem.

I have collected the myodbc.log, the output I get from Worldship, and
the MySQL describe output about the table I'm attempting to insert



Brandon D. Valentine

MySQL ODBC Mailing List
For list archives:
To unsubscribe:

Report this message