Error codes and diags not returned on error, w/ workaround

[uiteoi]

On error, the error parameter in callbacks does not contain any useful information for debugging queries.

I currently work around this issue using TRY blocks:

BEGIN TRY
  <original statement>
END TRY BEGIN CATCH
  SELECT ERROR_NUMBER() AS '__error', ERROR_MESSAGE() AS 'message', ERROR_SEVERITY() AS 'severity', ERROR_STATE() AS 'state'
END CATCH

[wread]

Did you try getting error information via callbacks? Here's one example:

    Connection.queryRaw(tsql, function (e, r) {
        if (e) {
            console.log("\nquery FAILED with this error message:\n" + e.toString()));
            return;
        }

[uiteoi]

Before implementing this workaround I have tried many things including JSON.stringify( e ), and using the "develop" branch to see of this was fixed but nothing worked so I had to implement this workaround which works great until you come with a fix.

My workaround also requires to test the results that are then otherwise always valid for the first column name to match '__error'.

[jguerin]

We will be expanding the error generation in a future release, so that you see the entire error stack from the underlying ODBC driver. Thanks for the feedback!

[jkint]

In addition, each error should contain the individual elements in an object, similar to how your query above does it. There should be 3 elements: SQLSTATE, message, and native error code.

[uiteoi]

When a stored procedure is called there are a few additional information that would be useful, check this article for more info: http://msdn.microsoft.com/en-us/library/ms179495(v=sql.105).aspx

I don't know if these are available at the ODBC level but in any case these can be caught at the SQL level in a try..catch block.

Because this driver seems to be designed specifically for SQL Server, I think it would be fair to assume that some of these useful information be available as a convenience provided by the higher-level driver compared to a pure ODBC-level driver.

[jguerin]

Thanks for the feedback, we'll evaluate it when we start work on this feature :)