Bug #26935 Error code S1T00 is not documented
Submitted: 7 Mar 2007 20:19 Modified: 9 Mar 2007 11:22
Reporter: Joe Roberts Email Updates:
Status: Closed Impact on me:
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.12 OS:Microsoft Windows (Windows 2000 Server)
Assigned to: CPU Architecture:Any

[7 Mar 2007 20:19] Joe Roberts
The error code S1T00 does not seem to be documented. With the new driver, when SQLTables is called using a stale connection and SQErrorMessage is called to get the error code - the code returns S1T00 error code. This is new behavior that is not documented in the list of error codes returned.  I have found this error code discussed in bug reports and in forums but not in the Documentation.

How to repeat:
See the description.
[9 Mar 2007 10:35] Valeriy Kravchuk
Thank you for a reasonable documentation request. See bug #11846 for the example on how to get this error code. It should be clearly documented.
[9 Mar 2007 10:44] Tonci Grgin
Hi Joe and thanks for your report. 

S1T00 is ODBC Native State Error and I don't think MySQL should document it but will pass the report to Docs team for final decision.
[9 Mar 2007 11:22] MC Brown
Since this is not a C/ODBC or MySQL specific error, I have not added this to the table, but I have add an entry to the Errors and Problems FAQ in the C/ODBC manual (http://dev.mysql.com/doc/refman/5.1/en/myodbc-errors.html).