pg-query 0.0.1.0 → 0.0.1.1

raw patch · 4 files changed

+9/−4 lines, 4 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• CHANGELOG.md +6/−1
• pg-query.cabal +1/−1
• src/PgQuery.hs +2/−2
• src/PgQuery/Internal/Proto/PgQuery.hs too large to diff

@@ -1,5 +1,10 @@ # Changelog -## 0.1.0.0 -- YYYY-mm-dd+## 0.0.1.1 -- 2024-11-18++* Adjusted the Haddocks for `parseSql` as well as the references in+  `PgQuery.Internal.Proto.PgQuery`.++## 0.0.1.0 -- 2024-11-18  * First version.

@@ -5,7 +5,7 @@ -- see: https://github.com/sol/hpack  name:           pg-query-version:        0.0.1.0+version:        0.0.1.1 synopsis:       Parse PostgreSQL DDL and DML: Haskell bindings for libpg_query  description:    pg-query offers Haskell bindings for @<https://github.com/pganalyze/libpg_query libpg_query>@, which makes use of the actual PostgreSQL server source to parse SQL queries and return the internal PostgreSQL parse tree.

@@ -21,7 +21,7 @@ import PgQuery.Internal.Proto.PgQuery import PgQuery.Internal.Proto.PgQuery_Fields --- | Parses a SQL 'String', returning the internal PostgreSQL parse tree as a+-- | Parses SQL, returning the internal PostgreSQL parse tree as a --   'ParseResult'. -- --   Here's an example:@@ -35,7 +35,7 @@ --         Right result -> print result --   @ -----   To make meaningful use of the 'ParseResult', you'll want to make use of+--   To make meaningful use of the 'ParseResult', you'll want to use --   "Control.Lens" in conjunction with the functions provided in --   "PgQuery.Internal.Proto.PgQuery_Fields". See --   [here](https://hackage.haskell.org/package/lens-tutorial-1.0.5/docs/Control-Lens-Tutorial.html)

file too large to diff