pqi-conformance 1.0.0.1 → 1.0.1.0

raw patch · 4 files changed

+17/−11 lines, 4 filesdep ~pqiPVP ok

version bump matches the API change (PVP)

Dependency ranges changed: pqi

API changes (from Hackage documentation)

Files

• CHANGELOG.md +6/−0
• pqi-conformance.cabal +2/−2
• src/library/Pqi/Conformance/Operation/Notifies.hs +6/−6
• src/library/Pqi/Conformance/Reference.hs +3/−3

@@ -1,3 +1,9 @@+# v1.0.1.0++## Non-breaking++- Picked up `pqi` 1.1.0.0, which renamed `Notify`'s fields to `notifyRelname`/`notifyBePid`/`notifyExtra` to match `postgresql-libpq`+ # v1.0.0.1  Doc corrections.

@@ -1,6 +1,6 @@ cabal-version: 3.0 name: pqi-conformance-version: 1.0.0.1+version: 1.0.1.0 category: Database, PostgreSQL, Testing synopsis: Differential conformance tests for pqi adapters description:@@ -202,6 +202,6 @@     directory >=1.3 && <1.4,     hspec >=2.11 && <2.12,     postgresql-libpq >=0.11 && <0.12,-    pqi ^>=1.0,+    pqi ^>=1.1,     testcontainers-postgresql ^>=0.2,     text >=1.2 && <3,

@@ -2,10 +2,10 @@ -- and that @UNLISTEN@ stops delivery. -- -- The backend PID carried by a notification is connection-specific - the--- candidate and the reference are distinct backends - so 'bePid' is omitted+-- candidate and the reference are distinct backends - so 'notifyBePid' is omitted -- from the cross-adapter comparison. Each scenario that receives a -- notification instead asserts independently (per adapter) that--- @Pqi.bePid notification == backendPID connection@, verifying that the PID field+-- @Pqi.notifyBePid notification == backendPID connection@, verifying that the PID field -- is correctly populated without comparing it across adapters. module Pqi.Conformance.Operation.Notifies   ( spec,@@ -31,7 +31,7 @@         _ <- Pqi.exec connection "notify conformance_channel, 'payload-1'"         notification <- Pqi.notifies connection         pid <- Pqi.backendPID connection-        for_ notification \n -> Pqi.bePid n `shouldBe` pid+        for_ notification \n -> Pqi.notifyBePid n `shouldBe` pid         drained <- fmap channelAndPayload <$> Pqi.notifies connection         pure (fmap channelAndPayload notification, drained) @@ -44,8 +44,8 @@         second <- Pqi.notifies connection         third <- Pqi.notifies connection         pid <- Pqi.backendPID connection-        for_ first \n -> Pqi.bePid n `shouldBe` pid-        for_ second \n -> Pqi.bePid n `shouldBe` pid+        for_ first \n -> Pqi.notifyBePid n `shouldBe` pid+        for_ second \n -> Pqi.notifyBePid n `shouldBe` pid         pure (fmap channelAndPayload first, fmap channelAndPayload second, fmap channelAndPayload third)      it "stops delivery after unlisten" \conninfo ->@@ -55,4 +55,4 @@         _ <- Pqi.exec connection "notify conformance_channel, 'lost'"         fmap channelAndPayload <$> Pqi.notifies connection   where-    channelAndPayload notification = (Pqi.relname notification, Pqi.extra notification)+    channelAndPayload notification = (Pqi.notifyRelname notification, Pqi.notifyExtra notification)

@@ -204,9 +204,9 @@ fromNotify :: LibPQ.Notify -> Pqi.Notify fromNotify notification =   Pqi.Notify-    { Pqi.relname = LibPQ.notifyRelname notification,-      Pqi.bePid = fromIntegral (LibPQ.notifyBePid notification),-      Pqi.extra = LibPQ.notifyExtra notification+    { Pqi.notifyRelname = LibPQ.notifyRelname notification,+      Pqi.notifyBePid = fromIntegral (LibPQ.notifyBePid notification),+      Pqi.notifyExtra = LibPQ.notifyExtra notification     }  toFormat :: Pqi.Format -> LibPQ.Format