Re: [Sqlalchemy-tickets] [sqlalchemy] #2201: determine "is_disconnect()" state on exception object
Brought to you by:
zzzeek
From: sqlalchemy <mi...@zz...> - 2011-07-01 20:56:42
|
#2201: determine "is_disconnect()" state on exception object for failed connection attempt ? ---------------------------------+------------------------------------------ Reporter: guest | Owner: zzzeek Type: enhancement | Status: closed Priority: medium | Milestone: 0.7.2 Component: oracle | Severity: major - 1-3 hours Resolution: fixed | Keywords: Status_field: completed/closed | ---------------------------------+------------------------------------------ Changes (by zzzeek): * status: new => closed * resolution: => fixed * status_field: not decided upon => completed/closed Comment: rd1c52060ea1e . This is a significant feature and behavioral change, would you mind upgrading to 0.7 or implementing a workaround if you're stuck on 0.6 for now ? if you have exception catching code that looks at the flag, then tries a re-do, just also check for ORA-01033. ORA-12541 is more controversial. Suppose you put the wrong host in ? Generally its very tough to classify an error that occurs on first connect as a "retryable" condition. Only if you've connected to that host already, and the connection drops, can you really be sure that a change on the previously correct DB host is the cause of the error. ORA-01033 is actually kind of special here - it means you did actually connect to a TNS listener successfully, just that the DB wasn't available. -- Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2201#comment:6> sqlalchemy <http://www.sqlalchemy.org/> The Database Toolkit for Python |