Bug #26295 | MyODBC Unspecified error returned when executing bad SQL syntax | ||
---|---|---|---|
Submitted: | 12 Feb 2007 21:03 | Modified: | 28 Feb 2008 22:56 |
Reporter: | Erica Moss | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 3.51, 5.1.1 | OS: | Windows (win xp) |
Assigned to: | Jim Winstead | CPU Architecture: | Any |
[12 Feb 2007 21:03]
Erica Moss
[19 Oct 2007 17:28]
Erica Moss
Tested with 3.51.20 and 5.1.0. Still returning undefined ADO error numbers although 5.1 now returns the same code as 3.51 which is: -2147217900 The list of defined errors is found here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdconadoerrorr... If one of these could be thrown it would be desirable. Test case has been added to: connectors-svnroot/odbc-testing/ado-conformance/trunk/bugs/26295.vbs
[23 Nov 2007 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[13 Dec 2007 23:25]
Erica Moss
Susanne: sorry didn't see your question. No 5.1 just returns the same bad error that 3.51 did, which is to say unspecified. It would be more appropriate to throw something like adErrInvalidArgument which is found in the list of ADO errors I posted. I'm not sure that this is within the control of the driver though.
[2 Jan 2008 23:38]
Jess Balint
We're returning 37000, which is the correct state for the ODBC 2 API (which is requested explicitely). I'm not sure how the OleDB layer is mapping the ODBC SQL state.
[28 Feb 2008 22:56]
Jim Winstead
This is correct, it is an OLE DB error code: DB_E_ERRORSINCOMMAND. The note here explains that OLE DB errors may be returned: http://msdn2.microsoft.com/en-us/library/ms806224.aspx