Skip to content

Releases: seancorfield/next-jdbc

1.2.731

04 Oct 22:33
Compare
Choose a tag to compare
  • Fix #181 by supporting option-wrapped connectables in execute-batch!.
  • Address #179 by improving documentation around connection pool initialization.
  • Update build-clj to v0.5.0.

1.2.724

25 Sep 22:46
Compare
Choose a tag to compare
  • Make next.jdbc compatible with GraalVM 22+ (PR #178, @FieryCod).
  • Address #177 by adding an important performance tip for Oracle.
  • Update most of the JDBC drivers for testing; make it easier to test MariaDB's driver;

1.2.709

31 Aug 01:26
Compare
Choose a tag to compare
  • Fix #174 by removing :property-separator from "etc" map and defaulting H2 to ";" for this.
  • Switch to tools.build for running tests and JAR building etc.

1.2.689

02 Aug 01:59
Compare
Choose a tag to compare

Primarily a documentation update release!

Enhancements:

  • Address #173 by extending DatafiableRow to ResultSet so there's a public method to call on (rows of) a JDBC result set directly.

Documentation:

  • Address #171 by clarifying that you cannot use clojure.java.jdbc functions inside next.jdbc/with-transaction and discuss how to migrate transaction-based code in the Migration guide.
  • Address #169 by expanding the description of with-transaction in Getting Started.
  • Cross-link to HoneySQL documentation for JSON/JSONB manipulation.
  • Remove superfluous prev/next links in docs (cljdoc does this automatically now).

Maintenance:

  • Update depstar, test-runner, and CI versions. Add example build.clj to run tests in a subprocess (purely educational).

1.2.674

17 Jun 05:52
Compare
Choose a tag to compare
  • Fix #167 by adding :property-separator to next.jdbc.connection/dbtypes and using it in jdbc-url.
  • Address #166 by adding next.jdbc/with-logging to create a wrapped connectable that will invoke logging functions with the SQL/parameters and optionally the result or exception for each operation.
  • Fix :unit_count references in Getting Started (were :unit_cost).
  • Update test-runner.

Release 1.2.659

05 May 19:51
Compare
Choose a tag to compare
  • Address #164 by making clj-commons/camel-snake-kebab an unconditional dependency. [Being a conditional dependency that could be brought in at runtime caused problems with GraalVM-based native compilation as well as with multi-project monorepos]
  • Add Tips & Tricks section about working with PostgreSQL "interval" types (via PR #163 from @snorremd).
  • Address #162 by adding GraalVM to the test matrix (thank you @DeLaGuardo).
  • Update several dependency versions.

Release 1.1.646

16 Mar 00:16
Compare
Choose a tag to compare

Adds a new arity to execute-batch! to accept a connectable (datasource or connection) and a SQL string, so that the work of creating the PreparedStatement is handled automatically (and the connection is created/closed automatically if needed). Fixes #161.

Release 1.1.643

06 Mar 23:19
Compare
Choose a tag to compare
  • Change coordinates to com.github.seancorfield/next.jdbc (although new versions will continue to be deployed to seancorfield/next.jdbc for a while -- see the Clojars Verified Group Names policy).
  • Documented next.jdbc.transaction/*nested-tx* more thoroughly since that difference from clojure.java.jdbc has come up in conversation a few times recently.
  • Fix #158 by documenting (and testing) :allowMultiQueries true as an option for MySQL/MariaDB to allow multiple statements to be executed and multiple result sets to be returned.
  • Fix #157 by copying next.jdbc.prepare/execute-batch! to next.jdbc/execute-batch! (to avoid a circular dependency that previously relied on requiring next.jdbc.result-set at runtime -- which was problematic for GraalVM-based native compilation); next.jdbc.prepare/execute-batch! is deprecated: it will continue to exist and work, but is no longer documented. In addition, next.jdbc.prepare/execute-batch! now relies on a private volatile! in order to reference next.jdbc.result-set/datafiable-result-set so that it is GraalVM-friendly. Note: code that requires next.jdbc.prepare and uses execute-batch! without also requiring something that causes next.jdbc.result-set to be loaded will no longer return generated keys from execute-batch! but that's an almost impossible path since nearly all code that uses execute-batch! will have called next.jdbc/prepare to get the PreparedStatement in the first place.

Release 1.1.613

05 Nov 20:49
Compare
Choose a tag to compare

Fixes a bug with how camel-snake-kebab is automatically made available, as part of an uberjar.

Release 1.1.610

19 Oct 18:23
Compare
Choose a tag to compare

Enhancements:

  • Adds next.jdbc.result-set/reducible-result-set and next.jdbc.result-set/foldable-result-set for users who want more control over processing result sets obtained from database metadata.
  • datafiable-result-set can now be called without the connectable and/or opts arguments: a nil connectable now disables foreign key navigation in datafied results (rather than throwing an obscure exception).
  • Support "duckdb" in next.jdbc.connection/dbtypes #140
  • Use thunks instead of vectors for next.jdbc.types/as-* functions, so that wrapped values do not get unpacked by HoneySQL.