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

..

access

- Changed the scheme used to generate truncated

2010-07-21 11:33:47 -04:00

firebird

- idle 78-char adjustments

2010-07-03 18:55:29 -04:00

informix

- idle 78-char adjustments

2010-07-03 18:55:29 -04:00

maxdb

- idle 78-char adjustments

2010-07-03 18:55:29 -04:00

mssql

reformatting /cleanup of column type docs, including [ticket:1858]

2010-08-01 15:00:58 -04:00

mysql

- The generated index name also is based on

2010-08-02 01:12:03 -04:00

oracle

- More tweaks to cx_oracle Decimal handling.

2010-07-14 14:50:45 -04:00

postgresql

- Changed the scheme used to generate truncated

2010-07-21 11:33:47 -04:00

sqlite

- Calling fetchone() or similar on a result that

2010-08-03 11:55:12 -04:00

sybase

- Changed the scheme used to generate truncated

2010-07-21 11:33:47 -04:00

__init__.py

- idle 78-char adjustments

2010-07-03 18:55:29 -04:00

postgres.py

- added "ddl" argument to the "on" callable of DDLElement [ticket:1538]

2009-10-12 00:11:00 +00:00

type_migration_guidelines.txt

- types.Binary is renamed to types.LargeBinary, it only

2010-01-23 19:44:06 +00:00