Product suggestion: inherit SAException from DBException

2

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...

asked 11 Mar '14, 04:55

Martin's gravatar image

Martin
8.9k●127●164●253
accept rate: 14%

One Answer:
active answersoldest answersnewest answerspopular answers
1

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!

permanent link

answered 30 Jun '15, 03:07

Martin's gravatar image

Martin
8.9k●127●164●253
accept rate: 14%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

learn more about Markdown

Question tags:

×74

question asked: 11 Mar '14, 04:55

question was seen: 1,624 times

last updated: 30 Jun '15, 03:07

Related questions

ASA9, .NET provider close connection problem

.NET web api accessing SQL Anywhere

external environment clr call succeeds without effort

SQLE_TOO_MANY_TEMP_TABLES - random error

Using data provider for EF4.x and EF6 in parallel

Store dblgde17.dll and dblgen17.dll in different directory (ADO.NET)

Inserting row through .NET ODBC driver

object o = myCmd.ExecuteScalar() unexpectedly returns null?

SATransaction with using statement

Database Driven Application requires SQLA Service Restart to See Changes