ITADN
seancorfield/next-jdbc

版本发布 8

1.3.1093v1.3.1093
? · 2026-01-31

* Address [#312](https://github.com/seancorfield/next-jdbc/issues/312) by adding support for `'hikari-cp` in `next.jdbc.connection/->pool`. * Update `java.data` to 1.4.120. * Update dev/test deps (CLI 1.12.4.1602).

1.3.1070v1.3.1070
? · 2025-09-06

This is a minor doc refresh and switches my test/build infrastructure over to Babashka: * Address [#307](https://github.com/seancorfield/next-jdbc/issues/307) by documenting the use of `next.jdbc.types/as-other` for binding parameters, to work around PostgreSQL's implicit casts, in **Tips & Tricks**. Thanks to [Peter Bex](https://github.com/sjamaan) for alerting me to this issue. * Noted that DuckDB returns an empty string from `.getTableName()` so you cannot get qualified maps with DuckDB. * Assume `bb` for testing/building; add `bb.edn`; switch GitHub Actions to use `bb`. * Fix clj-kondo lint issues in source files (`reify` calls in `next.jdbc.result-set`). * Update dev/test deps.

1.3.1002v1.3.1002
? · 2025-03-06

* Address [#296](https://github.com/seancorfield/next-jdbc/issues/296) by adding an explicit check (and `throw`) for `sql-params` in `next.jdbc` functions. * Address [#295](https://github.com/seancorfield/next-jdbc/issues/295) by providing a way to tell `next.jdbc` that certain options should be passed "as-is" in the `Properties` object when creating a `Connection` -- `:next.jdbc/as-is-properties` accepts a sequence (or set) of keywords, identifying properties that should not be converted to strings. * Fix [#181](https://github.com/seancorfield/next-jdbc/issues/181) (again!) by adding `Wrapped` protocol as a way for `DefaultOptions` and `SQLLogging` to consistently expose the underlying connectable, even when nested.

1.3.994v1.3.994
? · 2025-01-28

* Fix [#293](https://github.com/seancorfield/next-jdbc/issues/293) by no longer `locking` on the `Connection` retrieved from a `DataSource`. * Fix documentation examples of `execute-batch!` via PR [#292](https://github.com/seancorfield/next-jdbc/pull/292) from [@devurandom](https://github.com/devurandom). * Update `java.data` to 1.3.113. * Beef up bit/boolean tests and enable them for XTDB.

1.3.981v1.3.981
? · 2024-12-14

* Address [#291](https://github.com/seancorfield/next-jdbc/issues/291) by adding an XTDB section to **Tips & Tricks**. * Added XTDB as a supported database for testing via PR [#290](https://github.com/seancorfield/next-jdbc/pull/290). _Note: not all features are tested against XTDB due to several fundamental differences in architecture, mostly around primary key/generated keys and lack of DDL operations (since XTDB is schemaless)._ * Update dev/test dependencies.

1.3.967v1.3.967
? · 2024-12-03

* Address [#288](https://github.com/seancorfield/next-jdbc/issues/288) by adding speculative support for `:dbtype "xtdb"`. * Fix [#287](https://github.com/seancorfield/next-jdbc/issues/287) by merging user-supplied options over `:return-keys true`. * Fix [#282](https://github.com/seancorfield/next-jdbc/issues/282) by tracking raw `Connection` objects for active TXs, which relaxes several of the conditions around nested transactions. * Replace `assert` calls with proper validation, throwing `IllegalArgumentException` on failure. * Removed (experimental) `:name-fn` option since the driver for it no longer exists (qualified columns names in XTDB).

1.3.955v1.3.955
? · 2024-10-06

* Address [#285](https://github.com/seancorfield/next-jdbc/issues/285) by setting the default Clojure version to the earliest supported (1.10.3) to give a better hint to users. * Update PostgreSQL **Tips & Tricks** example code to fix possible NPE. PR [#284](https://github.com/seancorfield/next-jdbc/pull/284) from [@ExNexu](https://github.com/ExNexu). * Address [#283](https://github.com/seancorfield/next-jdbc/issues/283) by adding a note in the documentation, linking to the PostgreSQL bug report about `ANY(array)`. * Address [#269](https://github.com/seancorfield/next-jdbc/issues/269) by adding `:name-fn` as an option (primarily for the SQL builder functions, but also for result set processing); the default is `clojure.core/name` but you can now use `next.jdbc.sql.builder/qualified-name` to preserve the qualifier. * Update testing deps; `docker-compose` => `docker compose`.

1.3.939v1.3.939
? · 2024-05-18

* Fix [#280](https://github.com/seancorfield/next-jdbc/issues/280) by allowing `-` as well as `_` in `nav` foreign key names. * Address [#279](https://github.com/seancorfield/next-jdbc/issues/279) by adding the missing documentation. * Address [#278](https://github.com/seancorfield/next-jdbc/issues/278) by fixing link in options page. * Update dev dependencies, including testing against Clojure 1.12 Alpha 11.