Releases: dymmond/databasez
Releases · dymmond/databasez
Version 0.11.1
Version 0.11.0
Added
- Add support for jdbc reflection.
Version 0.10.2
Fixed
- Fix transactions in multi-threading contexts.
Changed
- The transaction stack contains the backend too.
Removed
- Remove
ACTIVE_TRANSACTIONS
ContextVar plus tests for it. It became unreliable with multithreading.
Version 0.10.1
Added
poll_interval
parameter (only relevant when using multithreading).
Fixed
- Improved thread-safety.
- full_isolation was not passed through in TestClient.
Version 0.10.0
Added
full_isolation
parameter. Isolate the force_rollback Connection in a thread.- Timeouts for operations.
Fixed
batched_iterate
interface ofConnection
differed from the one ofDatabase
.iterate
interface ofConnection
differed from the one ofDatabase
.- Hooks were called on automatically created Database objects.
- More multithreading safety.
Version 0.9.7
Added
- It is now possible to use connect(), disconnect() instead of a async contextmanager in multi-loop calls (multithreading).
Fixed
- Database calls are forwarded to subdatabase when possible. This unbreaks using not the returned database object.
force_rollback
works also in multi-loop call (multithreading).
Version 0.9.6
Fixed
- Databasez is now threadsafe (and multiloop safe).
Version 0.9.5
Changed
- Extract more options by default from query options.
Fixed
disconnect_hook
was called too early.connect_hook
was called too late.pos
not passed through in fetch_one.
Version 0.9.4
Changed
- Implement iterate in sqlalchemy base class (before it was a forward to batched_iterate).
Fixed
- iterate and batched_iterate misconfigure connection.
Version 0.9.3
Added
- Add lazy_setup parameter for testclient.
disconnect
andconnect
return if they performed the setup/cleanup.- Add backward compatible overwrites of defaults to the TestClient.
Fixed
- Restore eager setup behavior in testclient.
- Fix drop_dabase with postgresql.
- Fix setup/disconnect hangups.
- Fix ancient docs deps.