on 2014 Mar 11 4:55 AM
In .net all other database client access techniques use DBException as the base for the individual XXXException, only SAException is inherited from Exception. This makes it very difficult in a program using mixed client access technologies to catch a database exception accordingly. For example the DBException provides a general ErrorCode property, which is legacy named NativeError for SAException...
The documentation still reads:
public class SAException : System.Exception
but the a current SQLA 16 assembly now says:
public class SAException : System.Data.Common.DbException
so obviously my product suggestion was implemented.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
77 | |
10 | |
10 | |
10 | |
10 | |
9 | |
8 | |
7 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.