esqueleto 3.5.3.0 → 3.5.3.1

raw patch · 4 files changed

+18/−2 lines, 4 filesdep ~timePVP ok

version bump matches the API change (PVP)

Dependency ranges changed: time

API changes (from Hackage documentation)

Files

• README.md +1/−1
• changelog.md +7/−0
• esqueleto.cabal +1/−1
• src/Database/Esqueleto/Internal/Internal.hs +9/−0

@@ -488,5 +488,5 @@ mysql> CREATE DATABASE esqutest; mysql> CREATE USER 'travis'@'localhost'; mysql> ALTER USER 'travis'@'localhost' IDENTIFIED BY 'esqutest';-mysql> GRANT ALL ON esqutest.* TO 'travis';+mysql> GRANT ALL ON esqutest.* TO 'travis'@'localhost'; ```

@@ -1,3 +1,10 @@++3.5.3.1+=======+- @jappeace+  - [#303](https://github.com/bitemyapp/esqueleto/pull/303)+      - Added docs for delete function for new experimental API.+ 3.5.3.0 ======= - @m4dc4p

@@ -1,7 +1,7 @@ cabal-version: 1.12  name:           esqueleto-version:        3.5.3.0+version:        3.5.3.1 synopsis:       Type-safe EDSL for SQL queries on persistent backends. description:    @esqueleto@ is a bare bones, type-safe EDSL for SQL queries that works with unmodified @persistent@ SQL backends.  Its language closely resembles SQL, so you don't have to learn new concepts, just new syntax, and it's fairly easy to predict the generated SQL and optimize it for your backend. Most kinds of errors committed when writing SQL are caught as compile-time errors---although it is possible to write type-checked @esqueleto@ queries that fail at runtime.                 .

@@ -2618,6 +2618,15 @@ -- 'from' $ \\(appointment :: 'SqlExpr' ('Entity' Appointment)) -> -- return () -- @+--+-- ==== "Database.Esqueleto.Experimental":+--+-- @+--  delete $ do+--    userFeature <- from $ table @UserFeature+--    where_ ((userFeature ^. UserFeatureFeature) `notIn` valList allKnownFeatureFlags)+-- @+-- delete     :: (MonadIO m)     => SqlQuery ()