Mailing List
Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
MySQL++ - Programming with the C++ API to MySQL
ODBC - ODBC with the MySQL Connector/ODBC driver
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
• mysql openssl Question
• mysql:it 's a db not a dbms how it 's possible?!
• Does the binary log enabling affect the MySQL performances?
• Strange behavior, Table Level Permission
• FULLTEXT query format question
• Preventing Duplicate Entries
• Comparing and writing out BLOBS
• Executing MySQL Commands From Within C Program
• Can 't access mysql after kernel upgrade
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Downgrade Mysql from 4 to 3 23
• MySQL Cluster Software
• mysql test 4 1 fails with the gis test
• ERROR 2002: Can 't connect to local MySQL server through socket
• Getting Identity after INSERT
• Update one field with more fields from another table
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• mysql have same function mthod as Oracle decode()
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
EXPLAIN output on 7.5.0.8 and ODBC connection pooling

EXPLAIN output on 7.5.0.8 and ODBC connection pooling

2004-04-03       - By iml-sapdb@(protected)

 Back
Reply:     1     2  



Howdy all,

On Wiin32 (Windows XP or Windows 2000) with latest MaxDB 7.5.0.8 driver and
server...  two systems (one server, one client).  Using the
Unicode ODBC driver.

If I do these two queries from the same connection:

EXPLAIN SELECT field FROM TABLE
SELECT * FROM SHOW

I get my explain output... however, it only works if ODBC Connection Pooling is
enabled on the MaxDB ODBC driver.  If I turn off ODBC driver
connection pooling, it always fails saying that there is no SHOW table.

Also I'm still intersted in why one has to do the "SELECT * FROM SHOW" in the
first place.  I notice that the Python sample (posted previously
on the mailing list) does not have to do this.  Does the python driver
internally do the SELECT FROM SHOW  'automagically' and the ODBC
driver does not?

Reference python explain.py code: http://lists.mysql.com/maxdb/9229

Thank you.

 Stephen Gutknecht
 full time traveler with home on wheels
 currently in Irving Texas, USA




--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=mysql@(protected)