From 0484dfb8d489d46f947f617f983214b08da352cb Mon Sep 17 00:00:00 2001 From: parsonsmatt Date: Sun, 29 Mar 2020 10:42:23 -0600 Subject: [PATCH] v3.3.3.0 --- changelog.md | 7 +++++++ esqueleto.cabal | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/changelog.md b/changelog.md index fdecf6d..e0a053e 100644 --- a/changelog.md +++ b/changelog.md @@ -1,3 +1,10 @@ +3.3.3.0 +======== +- @belevy + - [#177](https://github.com/bitemyapp/esqueleto/pull/172) - Introduce new + experimental module for joins, set operations (eg UNION), and safer queries + from outer joins. + 3.3.2 ======== diff --git a/esqueleto.cabal b/esqueleto.cabal index 2645f28..bba5ed8 100644 --- a/esqueleto.cabal +++ b/esqueleto.cabal @@ -1,7 +1,7 @@ cabal-version: 1.12 name: esqueleto -version: 3.3.2 +version: 3.3.3.0 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. .