DBAL-663: [GH-411] Implement SQL Anywhere driver exception conversion #1883

Closed
doctrinebot opened this Issue Nov 14, 2013 · 2 comments

2 participants

@doctrinebot

Jira issue originally created by user @doctrinebot:

This issue is created automatically through a Github pull request on behalf of deeky666:

Url: #411

Message:

This fixes the SQL Anywhere driver to implement the new exception conversion.
The ExceptionTest::testConnectionException() test still fails though as exceptions occurring during connect are thrown in Connection::connect() which is not caught and transformed into a wrapped DBALException. I feel like this is an implementation error in either Connection or a false assumption in ExceptionTest::testConnectionException(). At least I think this is not a driver problem. Maybe there should be a DBALException::driverExceptionDuringConnect() that is called if an exception is raised in Connection::connect().

@doctrinebot

Comment created by @doctrinebot:

A related Github Pull-Request [GH-411] was closed:
#411

@doctrinebot

Issue was closed with resolution "Fixed"

@doctrinebot doctrinebot added the Bug label Dec 7, 2015
@beberlei beberlei was assigned by doctrinebot Dec 7, 2015
@doctrinebot doctrinebot added this to the 2.5 milestone Dec 7, 2015
@doctrinebot doctrinebot closed this Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment