[EMAIL PROTECTED] wrote:
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?

- ODBC looks for a SELECT and then adds a DECLARE CURSOR to specify the cursor name
- EXPLAIN is not detected as a statement returning a result set and DECLARE CURSOR won't work anyway, so the default name for EXPLAIN statement (SHOW) is generated by the kernel
- both the JDBC and the Python driver were too lazy to even look for a SELECT, so they expect the kernel to tell them the name of a possible result set in the return packet


Daniel Dittmar

--
Daniel Dittmar
SAP Labs Berlin
[EMAIL PROTECTED]


-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to