Bug #2540 SQLStatistics does not conform to the standard
Submitted: 28 Jan 2004 3:39 Modified: 23 Feb 2004 12:31
Reporter: SINISA MILIVOJEVIC Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:any OS:Any (any)
Assigned to: Peter Harvey CPU Architecture:Any

[28 Jan 2004 3:39] SINISA MILIVOJEVIC
Description:
SQLStatistics returns error instead of the empty set if a table name is not correctly specified.

How to repeat:
SQLStatistics returns error instead of the empty set if a table name is not correctly specified.
[23 Feb 2004 12:31] Peter Harvey
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Additional info:

I have carried out various tests and have noticed a number of issues surrounding SQLStatistics. For example; I have shown differences in behaviour between; MS Access, MS SQL v7, and MySQL/MyODBC. However; I was unable to cause my calls to SQLStatistics in MyODBC to return errors regardless of how malformed the arguments.

It would help if the customer were to provide a specific example of how SQLStatistics is being called. Also; I suspect that the error may lie in such things as a bad statement handle so supplying the value of the return code would also help.

My testing on...

- MyODBC v3.51 for XP from BK
- MySQL v4.0.17 for Linux from web download