Prep for 1.0.384 release
This commit is contained in:
parent
b58cf51af5
commit
4ab0ecd7df
4 changed files with 9 additions and 9 deletions
|
|
@ -4,19 +4,19 @@ Only accretive/fixative changes will be made from now on.
|
|||
|
||||
## Unreleased Changes
|
||||
|
||||
The following changes have been committed to the **master** branch since the 1.0.next release:
|
||||
The following changes have been committed to the **master** branch since the 1.0.384 release:
|
||||
|
||||
None.
|
||||
|
||||
## Stable Builds
|
||||
|
||||
* 2020-02-28 -- 1.0.next
|
||||
* 2020-02-28 -- 1.0.384
|
||||
* Add PostgreSQL streaming option information to **Tips & Tricks** (#87).
|
||||
* Minor documentation fixes (including #85, #92, #93).
|
||||
* Improve `Unknown dbtype` exception message (to clarify that `:classname` is also missing, #90).
|
||||
* Fix #88 by using 1-arity `keyword` call when table name unavailable (or `:qualifier-fn` returns `nil` or an empty string); also allows `:qualifier-fn` function to be called on empty table name (so `:qualifier-fn (constantly "qual")` will now work much like `clojure.java.jdbc`'s `:qualifier "qual"` worked).
|
||||
* Address #89, #91 by making minor performance tweaks to `next.jdbc.result-set` functions.
|
||||
* Planning to move to MAJOR.MINOR.COMMITS versioning scheme (1.0.next).
|
||||
* Planning to move to MAJOR.MINOR.COMMITS versioning scheme (1.0.384).
|
||||
|
||||
* 2019-12-20 -- 1.0.13
|
||||
* Fix #82 by adding `clojure.java.data`-based support for setting arbitrary properties on `Connection` and `PreparedStatement` objects, post-creation. Note: this uses the Java reflection API under the hood.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ The latest versions on Clojars and on cljdoc:
|
|||
|
||||
[](https://clojars.org/seancorfield/next.jdbc) [](https://cljdoc.org/d/seancorfield/next.jdbc/CURRENT)
|
||||
|
||||
This documentation is for **master** since the 1.0.next release -- [see the CHANGELOG](CHANGELOG.md).
|
||||
This documentation is for **master** since the 1.0.384 release -- [see the CHANGELOG](CHANGELOG.md).
|
||||
|
||||
* [Getting Started](/doc/getting-started.md)
|
||||
* [Migrating from `clojure.java.jdbc`](/doc/migration-from-clojure-java-jdbc.md)
|
||||
|
|
|
|||
|
|
@ -9,12 +9,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:
|
||||
|
||||
```clojure
|
||||
{seancorfield/next.jdbc {:mvn/version "1.0.13"}}
|
||||
{seancorfield/next.jdbc {:mvn/version "1.0.384"}}
|
||||
```
|
||||
for `deps.edn` or:
|
||||
|
||||
```clojure
|
||||
[seancorfield/next.jdbc "1.0.13"]
|
||||
[seancorfield/next.jdbc "1.0.384"]
|
||||
```
|
||||
for `project.clj` or `build.boot`.
|
||||
|
||||
|
|
@ -29,7 +29,7 @@ For the examples in this documentation, we will use a local H2 database on disk,
|
|||
```clojure
|
||||
;; deps.edn
|
||||
{:deps {org.clojure/clojure {:mvn/version "1.10.1"}
|
||||
seancorfield/next.jdbc {:mvn/version "1.0.13"}
|
||||
seancorfield/next.jdbc {:mvn/version "1.0.384"}
|
||||
com.h2database/h2 {:mvn/version "1.4.199"}}}
|
||||
```
|
||||
|
||||
|
|
|
|||
4
pom.xml
4
pom.xml
|
|
@ -3,7 +3,7 @@
|
|||
<modelVersion>4.0.0</modelVersion>
|
||||
<groupId>seancorfield</groupId>
|
||||
<artifactId>next.jdbc</artifactId>
|
||||
<version>1.0.next</version>
|
||||
<version>1.0.384</version>
|
||||
<name>next.jdbc</name>
|
||||
<description>The next generation of clojure.java.jdbc: a new low-level Clojure wrapper for JDBC-based access to databases.</description>
|
||||
<url>https://github.com/seancorfield/next-jdbc</url>
|
||||
|
|
@ -22,7 +22,7 @@
|
|||
<url>https://github.com/seancorfield/next-jdbc</url>
|
||||
<connection>scm:git:git://github.com/seancorfield/next-jdbc.git</connection>
|
||||
<developerConnection>scm:git:ssh://git@github.com/seancorfield/next-jdbc.git</developerConnection>
|
||||
<tag>v1.0.next</tag>
|
||||
<tag>v1.0.384</tag>
|
||||
</scm>
|
||||
<dependencies>
|
||||
<dependency>
|
||||
|
|
|
|||
Loading…
Reference in a new issue