Files
sqlalchemy/test/sql
Mike Bayer ddf4210552 - Calling fetchone() or similar on a result that
has already been exhausted, has been closed,
or is not a result-returning result now
raises ResourceClosedError, a subclass of
InvalidRequestError, in all cases, regardless
of backend.  Previously, some DBAPIs would
raise ProgrammingError (i.e. pysqlite), others
would return None leading to downstream breakages
(i.e. MySQL-python).

- Connection, ResultProxy, as well as Session use
ResourceClosedError for all "this
connection/transaction/result is closed" types of
errors.
2010-08-03 11:55:12 -04:00
..
2010-06-24 12:45:37 -04:00
2010-04-21 09:30:30 -04:00