Package: libmyodbc Version: 5.1.6-1 Severity: important
There are plenty of bugs in MyODBC, such as this one: http://bugs.mysql.com/bug.php?id=36441 In short, on my system (Debian-64 bit), SQLPrimaryKeys and SQLPrimaryKeysW will mangle the results of a table that has both a primary key and a unique key on another column. This has been fixed in MyODBC 5.1.7, which has been out since August 2010 ! They are now up to 5.1.9, and 5.1.10 may be released any day now. Is it time to resync with upstream? Thanks, Paul -- System Information: Debian Release: 6.0.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38.3 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libmyodbc depends on: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libltdl7 2.2.6b-2 A system independent dlopen wrappe ii libmysqlclient16 5.1.49-3 MySQL database client library ii odbcinst1debian2 2.2.14p2-1 Support library for accessing odbc ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages libmyodbc recommends: ii libiodbc2 3.52.6-4 iODBC Driver Manager ii unixodbc 2.2.14p2-1 ODBC tools libraries libmyodbc suggests no packages. -- debconf information: libmyodbc/addtoodbc: false
