Merge pull request #117 from bitemyapp/matt/remove-sql-qq
Remove QQ re-exports
This commit is contained in:
commit
b1f26af377
@ -1,6 +1,12 @@
|
||||
Unreleased
|
||||
========
|
||||
|
||||
2.7.0
|
||||
=======
|
||||
|
||||
- @parsonsmatt
|
||||
- [#117](https://github.com/bitemyapp/esqueleto/pull/117): Removed `sqlQQ` and `executeQQ` functions from export, fixing doc build and building with `persistent` >= 2.9
|
||||
|
||||
2.6.1
|
||||
=======
|
||||
|
||||
|
||||
@ -4,10 +4,10 @@ cabal-version: 1.12
|
||||
--
|
||||
-- see: https://github.com/sol/hpack
|
||||
--
|
||||
-- hash: c68a1e254e29c461cbf88a8a32c039563f3576cf439b9d947cb3d8dd3916e0e8
|
||||
-- hash: b9e04d2f75b2f0eaebcef3906057ae77f42a6455f7bd453c3f7ed399b1669e8e
|
||||
|
||||
name: esqueleto
|
||||
version: 2.6.1
|
||||
version: 2.6.2
|
||||
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.
|
||||
.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
name: esqueleto
|
||||
version: 2.6.1
|
||||
version: 2.7.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
|
||||
|
||||
@ -53,8 +53,6 @@ module Database.Esqueleto.Internal.PersistentImport
|
||||
rawQuery,
|
||||
rawQueryRes,
|
||||
rawSql,
|
||||
executeQQ,
|
||||
sqlQQ,
|
||||
askLogFunc,
|
||||
close',
|
||||
createSqlPool,
|
||||
|
||||
Loading…
Reference in New Issue
Block a user