Hi Thomas,

Yes, works in SQL Studio fine.

Based on the other replies, it appears that the EXPLAIN statement requires a
cursor and open connection.  In other words, it is not like a "SELECT"
statement that result rows can be read via a single read-only operation.

Daniel Dittmar posted a Python script sample on how to do this, I've not yet
had time to port to my dotNET application.

Any further word on the ODBC driver crash and the ability to run the ODBC
driver in debug without the need to answer the pop-up message (impossible
with IIS)?

Thanks.

  Stephen


-----Original Message-----
From: Koetter, Thomas Theodor [mailto:thomas.theodor.koetter@;sap.com] 
Sent: Wednesday, October 23, 2002 5:25 AM
To: 'Stephen Gutknecht (SAPDB)'; [EMAIL PROTECTED]
Subject: RE: ODBC on Win32 - EXPLAIN statement no output


Hi Stephen

Sorry for the delay ...

> -----Original Message-----
> From: Stephen Gutknecht (SAPDB) [mailto:IML-sapdb@;i405.com]
> Sent: Mittwoch, 16. Oktober 2002 17:29
[snip]
> I'm confused how one can get EXPLAIN output from a ODBC
> client program.  I
> am trying to automate performance study of my queries...
> 
> I get no result on my "EXPLAIN SELECT * FROM myTable WHERE
> FIELD1 IS NOT
> NULL" statements.  The statement executes without error, but 
> I do not get
> any result tables/rows.  I am executing the statement just 
> like I would a
> "SELECT"...
> 
> Based on hints from the archive, I have also tried doing a
> "SELECT * FROM
> SHOW" immediately following my EXPLAIN statement, but I get 
> an error about
> no SHOW table.


Hm, this is exactly the way it should work. Just I checked it
without problems. What happened if you send the explain-statement
in SQL Studio? Does it also return nothing?


Greetings  Thomas


----------------------------------------------
Dr. Thomas K�tter
SAP DB, SAP Labs Berlin


SAP DB is open source. Get it!    www.sapdb.org 


 
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to