Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• Subject: mysql openssl Question
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• Update one field with more fields from another table
• Subject: Getting Identity after INSERT
• ERROR 2002: Can 't connect to local MySQL server through socket
• mysql test 4 1 fails with the gis test
• Subject: MySQL Cluster Software
• Downgrade Mysql from 4 to 3 23
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Can 't access mysql after kernel upgrade
• Executing MySQL Commands From Within C Program
• Comparing and writing out BLOBS
• Subject: Re: Preventing Duplicate Entries
• FULLTEXT query format question
• Strange behavior, Table Level Permission
• Does the binary log enabling affect the MySQL performances?
• mysql:it 's a db not a dbms how it 's possible?!
• mysql have same function mthod as Oracle decode()
 
ODBC 3.51.22 not working with Systat

ODBC 3.51.22 not working with Systat

2007-11-29       - By Gary Lewis

 Back
Reply:     1     2     3     4  

Hi - I downloaded and installed mysql-connector-odbc-3 (See http://dbc-3.ora-code.com).51.22-win32.msi. The
OS is MS Windows XP Professional Version 2002 SP2. The installation
completed successfully. I used ODBC Data Source Administrator to create and
successfully test a DSN using the MySQL ODBC 3.51 driver.

What doesn't work is Systat (v 12.01.02) when I try to access a MySQL
database table via ODBC. It sees the Data Source I created, but it does not
list the database (ie, schema) or any tables. These are grayed out and just
hung.

Here's the last bit of the sql.log trace file:
SYSTAT          c40-f60 ENTER SQLGetData
 HSTMT               05082B88
 UWORD                       12
 SWORD                        1 <SQL_C_CHAR>
 PTR                 0x0012C18C
 SQLLEN                   128
 SQLLEN *            0x0012C20C
SYSTAT          c40-f60 EXIT  SQLGetData  with return code 0 (SQL_SUCCESS)
 HSTMT               05082B88
 UWORD                       12
 SWORD                        1 <SQL_C_CHAR>
 PTR                 0x0012C18C
 SQLLEN                   128
 SQLLEN *            0x0012C20C (0)
SYSTAT          c40-f60 ENTER SQLFetch
 HSTMT               05082B88
SYSTAT          c40-f60 EXIT  SQLFetch  with return code 100
(SQL_NO_DATA_FOUND)
 HSTMT               05082B88
SYSTAT          c40-f60 ENTER SQLFreeStmt
 HSTMT               05082B88
 UWORD                        1 <SQL_DROP>
SYSTAT          c40-f60 EXIT  SQLFreeStmt  with return code 0 (SQL_SUCCESS)
 HSTMT               05082B88
 UWORD                        1 <SQL_DROP>

And the myodbc.log file:
-- Query logging
--
--  Driver name: MySQL ODBC 3.51 Driver  Version: 03.51.22
-- Timestamp: 071129 11:24:18
SHOW TABLE STATUS ;
SHOW TABLE STATUS LIKE 't1';

What I'd like to figure out is if this is a MySQL ODBC Connector problem or
a Systat problem. I'm using a 30-day trial version of Systat, but it's
supposed to be a fully functional version.

Any help would be appreciated. Thanks.

Gary