Catching sql exceptions in a provider agnostic way

Question

I'm converting the Data Access Code in one of my Asp.Net projects To MSSQL from MySQL. I'm taking this opportunity to attempt to remove any dependencies on provider specific classes or namespaces.

So instead of working directly with MySqlCommand or SqlCommand classes, I'm using DbProviderFactories.GetFactory() methods to return DbCommand objects.

The one issue I'm having is I had code that trapped MySqlExpection exceptions. I'd like a provider agnostic way of trapping Sql exceptions. Is this possible?

Just to clarify, the exceptions you are catching are within the Data Layer or outside of it? — Jaime Mendes, Sep 01 '13 at 14:55
Sql implements DBexception. I assumed MSSQL does also. Did you try DBexceptoin? I don't have a MSSQL to test with. — paparazzo, Sep 01 '13 at 15:24
@Blam. The Syste.Data.Common.DBException class is exactly what I was looing for. IF you'd like to post that as an answer, I'll upvote it and accept it as the correct answer. — Aheho, Sep 01 '13 at 15:48

score 0 · Answer 1 · edited May 23 '17 at 12:29

0

Without great knowledge to the topic, my thought is that the exceptions are thrown from the concrete classes that provide access to the database. I could guess that some exceptions may be common by nature but other may not. I believe though that it is a good practice to get the specific error logged rather than some abstraction.

Check this SO question and MSDN for more info.

edited May 23 '17 at 12:29

Community

1
1

answered Sep 01 '13 at 15:11

V-Lamp

1,630
10
18

Jaime Mendes · Answer 2 · 2013-09-01T15:51:35.570

I would recommend something like this. This way, you can either throw an generic sql exception or throw your custom exception associated with a given logic, p.e., ConnectionTimedOutException.

catch(Exception ex)
{
    if(DbProviderFactories.GetException(ex) is CustomSQLException)
    {
        //logic here
    }
    throw;
}

//Factory method
public Exception GetException(Exception ex)
{
    Exception result;
    //Identifying which is the current one
    switch (CurrentProvider)
    {   
        case Provider.SQLServer: 
            //logic here
            result = new CustomSQLServerException(ex); //which extends CustomSQLException
            break;
        default:
            result = ex;
            break;
    }
    return result;
}

score 0 · Accepted Answer · edited Sep 01 '13 at 21:09

0

Sql implements DBexception. I assumed MSSQL does also.
Did you try DBexception?
I don't have a MSSQL to test with.

edited Sep 01 '13 at 21:09

Aheho

12,622
13
54
83

answered Sep 01 '13 at 18:06

paparazzo

44,497
23
105
176

Catching sql exceptions in a provider agnostic way

3 Answers3