Changelog for hasql-pool-1.4.1
1.4
- Migrated to
hasql-1.10 - Updated connection settings API to use monoid-based
Settingsinstead of list-based[Setting] - Updated error types to use
Hasql.Errorsmodule instead ofHasql.SessionandHasql.Connection - Changed session execution API from
Session.run session connectiontoConnection.use connection session - Error handling now uses
ConnectionSessionErrorfor connection-level issues instead ofClientError - Updated statement construction to use
Statement.preparableandStatement.unpreparableinstead of direct constructor - Hid the
Defaultsmodule from the public API
1.3
- Adapt to the new settings model of
hasql-1.9
1.2
- Migrated to
hasql-1.7 - Changed references to
QueryErrorin observations toSessionError
1.1
ReadyForUseConnectionStatusgot extended with theConnectionReadyForUseReasondetails.initSessionsetting added.
1
- Optional observability event stream added. Provides a flexible mechanism for monitoring the healthiness of the pool via logs and metrics.
- Configuration got isolated into a DSL, which will allow to provide new configurations without breaking backward compatibility.
0.10.1
- Avoid releasing connections on exceptions thrown in session
0.9
- Maximal lifetime added for connections. Allows to refresh the connections in time cleaning up the resources.
Breaking:
- The acquisition timeout is now non-optional.
- Moved to
DiffTimefor timeouts.
0.8.0.7
Fix excessive connections during releases due to race conditions.
0.8.0.5
Fix connections not returning to the pool on exceptions.
0.8.0.2
Fixed Windows build.
0.8
release became reusable. You can use it to destroy the whole pool (same as before), but now also you can use it to reset the connections.
Acquisition timeout added.
Breaking changes in API:
- Removed
PoolIsReleasedUsageError acquireextended with the acquisition timeout parameteracquireDynamicallyextended with the acquisition timeout parameter
0.7.2
Added support for dynamic connection configuration (issue #11).
0.7.1.2
Fixed connections not being released if they were in use during the call to release.
0.7.1
Added Exception for UsageError.
0.7
Simplified the implementation a lot by removing the notion of timeout.
Breaking:
- Removed the
Settingstype - Changed the signature of
acquire
0.6
Moved away from "resource-pool" and fixed the handling of lost connections.
Breaking:
- Changed the suffix of
UsageErrorconstructors fromErrortoUsageError - Added
PoolIsReleasedUsageError