prep for 1.3.925
Signed-off-by: Sean Corfield <sean@corfield.org>
This commit is contained in:
parent
3042079138
commit
39018404ab
5 changed files with 10 additions and 10 deletions
|
|
@ -2,7 +2,7 @@
|
||||||
|
|
||||||
Only accretive/fixative changes will be made from now on.
|
Only accretive/fixative changes will be made from now on.
|
||||||
|
|
||||||
* 1.3.next in progress
|
* 1.3.925 -- 2024-03-15
|
||||||
* Address [#275](https://github.com/seancorfield/next-jdbc/issues/275) by noting that PostgreSQL may perform additional SQL queries to produce table names used in qualified result set builders.
|
* Address [#275](https://github.com/seancorfield/next-jdbc/issues/275) by noting that PostgreSQL may perform additional SQL queries to produce table names used in qualified result set builders.
|
||||||
* Address [#274](https://github.com/seancorfield/next-jdbc/issues/274) by adding `next.jdbc.sql/aggregate-by-keys` as a convenient wrapper around `find-by-keys` when you want just a single aggregate value back (such as `count`, `max`, etc).
|
* Address [#274](https://github.com/seancorfield/next-jdbc/issues/274) by adding `next.jdbc.sql/aggregate-by-keys` as a convenient wrapper around `find-by-keys` when you want just a single aggregate value back (such as `count`, `max`, etc).
|
||||||
* Address [#273](https://github.com/seancorfield/next-jdbc/issues/273) by linking to [PG2](https://github.com/igrishaev/pg2) in the PostgreSQL **Tips & Tricks** section.
|
* Address [#273](https://github.com/seancorfield/next-jdbc/issues/273) by linking to [PG2](https://github.com/igrishaev/pg2) in the PostgreSQL **Tips & Tricks** section.
|
||||||
|
|
|
||||||
|
|
@ -8,8 +8,8 @@ The next generation of `clojure.java.jdbc`: a new low-level Clojure wrapper for
|
||||||
|
|
||||||
The latest versions on Clojars and on cljdoc:
|
The latest versions on Clojars and on cljdoc:
|
||||||
|
|
||||||
[](https://clojars.org/com.github.seancorfield/next.jdbc)
|
[](https://clojars.org/com.github.seancorfield/next.jdbc)
|
||||||
[](https://cljdoc.org/d/com.github.seancorfield/next.jdbc/CURRENT)
|
[](https://cljdoc.org/d/com.github.seancorfield/next.jdbc/CURRENT)
|
||||||
[](https://clojurians.slack.com/app_redirect?channel=sql)
|
[](https://clojurians.slack.com/app_redirect?channel=sql)
|
||||||
[](http://clojurians.net)
|
[](http://clojurians.net)
|
||||||
|
|
||||||
|
|
@ -20,7 +20,7 @@ The documentation on [cljdoc.org](https://cljdoc.org/d/com.github.seancorfield/n
|
||||||
* [Migrating from `clojure.java.jdbc`](https://cljdoc.org/d/com.github.seancorfield/next.jdbc/CURRENT/doc/migration-from-clojure-java-jdbc)
|
* [Migrating from `clojure.java.jdbc`](https://cljdoc.org/d/com.github.seancorfield/next.jdbc/CURRENT/doc/migration-from-clojure-java-jdbc)
|
||||||
* Feedback via [issues](https://github.com/seancorfield/next-jdbc/issues) or in the [`#sql` channel on the Clojurians Slack](https://clojurians.slack.com/messages/C1Q164V29/) or the [`#sql` stream on the Clojurians Zulip](https://clojurians.zulipchat.com/#narrow/stream/152063-sql).
|
* Feedback via [issues](https://github.com/seancorfield/next-jdbc/issues) or in the [`#sql` channel on the Clojurians Slack](https://clojurians.slack.com/messages/C1Q164V29/) or the [`#sql` stream on the Clojurians Zulip](https://clojurians.zulipchat.com/#narrow/stream/152063-sql).
|
||||||
|
|
||||||
The documentation on GitHub is for **develop** since the 1.3.909 release -- [see the CHANGELOG](https://github.com/seancorfield/next-jdbc/blob/develop/CHANGELOG.md) and then read the [corresponding updated documentation](https://github.com/seancorfield/next-jdbc/tree/develop/doc) on GitHub if you want. Older versions of `next.jdbc` were published under the `seancorfield` group ID and you can find [older seancorfield/next.jdbc documentation on cljdoc.org](https://cljdoc.org/versions/seancorfield/next.jdbc).
|
The documentation on GitHub is for **develop** since the 1.3.925 release -- [see the CHANGELOG](https://github.com/seancorfield/next-jdbc/blob/develop/CHANGELOG.md) and then read the [corresponding updated documentation](https://github.com/seancorfield/next-jdbc/tree/develop/doc) on GitHub if you want. Older versions of `next.jdbc` were published under the `seancorfield` group ID and you can find [older seancorfield/next.jdbc documentation on cljdoc.org](https://cljdoc.org/versions/seancorfield/next.jdbc).
|
||||||
|
|
||||||
This project follows the version scheme MAJOR.MINOR.COMMITS where MAJOR and MINOR provide some relative indication of the size of the change, but do not follow semantic versioning. In general, all changes endeavor to be non-breaking (by moving to new names rather than by breaking existing names). COMMITS is an ever-increasing counter of commits since the beginning of this repository.
|
This project follows the version scheme MAJOR.MINOR.COMMITS where MAJOR and MINOR provide some relative indication of the size of the change, but do not follow semantic versioning. In general, all changes endeavor to be non-breaking (by moving to new names rather than by breaking existing names). COMMITS is an ever-increasing counter of commits since the beginning of this repository.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -58,7 +58,7 @@ In the simple case, the `:columns` option expects a vector of keywords and each
|
||||||
|
|
||||||
> Note: `get-by-id` accepts the same options as `find-by-keys` but it will only ever produce one row, as a hash map, so sort order and pagination are less applicable, although `:columns` may be useful.
|
> Note: `get-by-id` accepts the same options as `find-by-keys` but it will only ever produce one row, as a hash map, so sort order and pagination are less applicable, although `:columns` may be useful.
|
||||||
|
|
||||||
As of 1.3.next, `aggregate-by-keys` exists as a wrapper around `find-by-keys`
|
As of 1.3.925, `aggregate-by-keys` exists as a wrapper around `find-by-keys`
|
||||||
that accepts the same options as `find-by-keys` except that `:columns` may not
|
that accepts the same options as `find-by-keys` except that `:columns` may not
|
||||||
be specified (since it is used to add the aggregate to the query).
|
be specified (since it is used to add the aggregate to the query).
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -25,7 +25,7 @@ These functions are described in more detail below. They are deliberately simple
|
||||||
|
|
||||||
If you prefer to write your SQL separately from your code, take a look at [HugSQL](https://github.com/layerware/hugsql) -- [HugSQL documentation](https://www.hugsql.org/) -- which has a `next.jdbc` adapter, as of version 0.5.1. See below for a "[quick start](#hugsql-quick-start)" for using HugSQL with `next.jdbc`.
|
If you prefer to write your SQL separately from your code, take a look at [HugSQL](https://github.com/layerware/hugsql) -- [HugSQL documentation](https://www.hugsql.org/) -- which has a `next.jdbc` adapter, as of version 0.5.1. See below for a "[quick start](#hugsql-quick-start)" for using HugSQL with `next.jdbc`.
|
||||||
|
|
||||||
As of 1.3.next, `aggregate-by-keys` exists as a wrapper around `find-by-keys`
|
As of 1.3.925, `aggregate-by-keys` exists as a wrapper around `find-by-keys`
|
||||||
that accepts the same options as `find-by-keys` and an aggregate SQL expression
|
that accepts the same options as `find-by-keys` and an aggregate SQL expression
|
||||||
and it returns a single value (the aggregate). `aggregate-by-keys` accepts the
|
and it returns a single value (the aggregate). `aggregate-by-keys` accepts the
|
||||||
same options as `find-by-keys` except that `:columns` may not be specified
|
same options as `find-by-keys` except that `:columns` may not be specified
|
||||||
|
|
@ -255,7 +255,7 @@ If no rows match, `find-by-keys` returns `[]`, just like `execute!`.
|
||||||
|
|
||||||
## `aggregate-by-keys`
|
## `aggregate-by-keys`
|
||||||
|
|
||||||
Added in 1.3.next, this is a wrapper around `find-by-keys` that makes it easier
|
Added in 1.3.925, this is a wrapper around `find-by-keys` that makes it easier
|
||||||
to perform aggregate queries::
|
to perform aggregate queries::
|
||||||
|
|
||||||
```clojure
|
```clojure
|
||||||
|
|
|
||||||
|
|
@ -11,12 +11,12 @@ It is designed to work with Clojure 1.10 or later, supports `datafy`/`nav`, and
|
||||||
You can add `next.jdbc` to your project with either:
|
You can add `next.jdbc` to your project with either:
|
||||||
|
|
||||||
```clojure
|
```clojure
|
||||||
com.github.seancorfield/next.jdbc {:mvn/version "1.3.909"}
|
com.github.seancorfield/next.jdbc {:mvn/version "1.3.925"}
|
||||||
```
|
```
|
||||||
for `deps.edn` or:
|
for `deps.edn` or:
|
||||||
|
|
||||||
```clojure
|
```clojure
|
||||||
[com.github.seancorfield/next.jdbc "1.3.909"]
|
[com.github.seancorfield/next.jdbc "1.3.925"]
|
||||||
```
|
```
|
||||||
for `project.clj` or `build.boot`.
|
for `project.clj` or `build.boot`.
|
||||||
|
|
||||||
|
|
@ -38,7 +38,7 @@ For the examples in this documentation, we will use a local H2 database on disk,
|
||||||
```clojure
|
```clojure
|
||||||
;; deps.edn
|
;; deps.edn
|
||||||
{:deps {org.clojure/clojure {:mvn/version "1.11.1"}
|
{:deps {org.clojure/clojure {:mvn/version "1.11.1"}
|
||||||
com.github.seancorfield/next.jdbc {:mvn/version "1.3.909"}
|
com.github.seancorfield/next.jdbc {:mvn/version "1.3.925"}
|
||||||
com.h2database/h2 {:mvn/version "2.2.224"}}}
|
com.h2database/h2 {:mvn/version "2.2.224"}}}
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue