hasql-pool 1 → 1.0.0.1
raw patch · 2 files changed
+10/−4 lines, 2 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
Files
hasql-pool.cabal view
@@ -1,6 +1,6 @@ cabal-version: 3.0 name: hasql-pool-version: 1+version: 1.0.0.1 category: Hasql, Database, PostgreSQL synopsis: Pool of connections for Hasql homepage: https://github.com/nikita-volkov/hasql-pool
src/library/other/Hasql/Pool/Config/Setting.hs view
@@ -52,7 +52,9 @@ -- -- You can use 'Hasql.Connection.settings' to construct it. ----- @\"postgresql://postgres:postgres@localhost:5432/postgres\"@ by default.+-- By default it is:+--+-- > "postgresql://postgres:postgres@localhost:5432/postgres" staticConnectionSettings :: Connection.Settings -> Setting staticConnectionSettings x = Setting (\config -> config {Config.connectionSettingsProvider = pure x})@@ -64,7 +66,9 @@ -- -- You can use 'Hasql.Connection.settings' to construct it. ----- @pure \"postgresql://postgres:postgres@localhost:5432/postgres\"@ by default.+-- By default it is:+--+-- > pure "postgresql://postgres:postgres@localhost:5432/postgres" dynamicConnectionSettings :: IO Connection.Settings -> Setting dynamicConnectionSettings x = Setting (\config -> config {Config.connectionSettingsProvider = x})@@ -76,7 +80,9 @@ -- If the provided action is not lightweight, it's recommended to use intermediate bufferring via channels like TBQueue to avoid occupying the pool management thread for too long. -- E.g., if the action is @'atomically' . 'writeTBQueue' yourQueue@, then reading from it and processing can be done on a separate thread. ----- @const (pure ())@ by default.+-- By default it is:+--+-- > const (pure ()) observationHandler :: (Observation -> IO ()) -> Setting observationHandler x = Setting (\config -> config {Config.observationHandler = x})