luciano/next-jdbc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge branch 'develop' of github.com:seancorfield/next-jdbc into develop

Browse source
This commit is contained in:
Sean Corfield 2021-01-23 15:53:05 -08:00
commit a3fe68e3d1
4 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/all-the-options.md
View file

@ -87,7 +87,7 @@ Not all databases or drivers support all of these options, or all values for any
> Note: If `plan`, `execute!`, or `execute-one!` are passed a `DataSource`, a "db spec" hash map, or a JDBC URL string, they will call `prepare` to create a `PreparedStatement`, so they will accept the above options in those cases. > Note: If `plan`, `execute!`, or `execute-one!` are passed a `DataSource`, a "db spec" hash map, or a JDBC URL string, they will call `prepare` to create a `PreparedStatement`, so they will accept the above options in those cases.
In addition the the above, `next.jdbc.prepare/execute-batch!` (which does **not** create a `PreparedStatement`) accepts an options hash map that can also contain the following: In addition to the above, `next.jdbc.prepare/execute-batch!` (which does **not** create a `PreparedStatement`) accepts an options hash map that can also contain the following:
* `:batch-size` -- an integer that determines how to partition the parameter groups for submitting to the database in batches, * `:batch-size` -- an integer that determines how to partition the parameter groups for submitting to the database in batches,
* `:large` -- a Boolean flag that indicates whether the batch will produce large update counts (`long` rather than `int` values), * `:large` -- a Boolean flag that indicates whether the batch will produce large update counts (`long` rather than `int` values),

2
src/next/jdbc/connection.clj
View file

@ -372,7 +372,7 @@
These options are supported: These options are supported:
* `:auto-commit` -- whether the connection should be set to auto-commit or not; * `:auto-commit` -- whether the connection should be set to auto-commit or not;
without this option, the defaut is `true` -- connections will auto-commit, without this option, the default is `true` -- connections will auto-commit,
* `:read-only` -- whether the connection should be set to read-only mode, * `:read-only` -- whether the connection should be set to read-only mode,
* `:connection` -- a hash map of camelCase properties to set on the connection, * `:connection` -- a hash map of camelCase properties to set on the connection,
via reflection, e.g., :autoCommit, :readOnly, :schema..." via reflection, e.g., :autoCommit, :readOnly, :schema..."

2
src/next/jdbc/datafy.clj
View file

@ -19,7 +19,7 @@
* `Statement` -- datafies as a bean. * `Statement` -- datafies as a bean.
Because different database drivers may throw `SQLException` for various Because different database drivers may throw `SQLException` for various
unimplemented or unavailable propertiies on objects in various states, unimplemented or unavailable properties on objects in various states,
the default behavior is to return those exceptions using the `:qualify` the default behavior is to return those exceptions using the `:qualify`
option for `clojure.java.data/from-java-shallow`, so for a property option for `clojure.java.data/from-java-shallow`, so for a property
`:foo`, if its corresponding getter throws an exception, it would instead `:foo`, if its corresponding getter throws an exception, it would instead

4
src/next/jdbc/result_set.clj
View file

@ -11,7 +11,7 @@
A broad range of result set builder implementation functions are provided. A broad range of result set builder implementation functions are provided.
Also provides the default implemenations for `Executable` and Also provides the default implementations for `Executable` and
the default `datafy`/`nav` behavior for rows from a result set. the default `datafy`/`nav` behavior for rows from a result set.
See also https://cljdoc.org/d/seancorfield/next.jdbc/CURRENT/api/next.jdbc.date-time See also https://cljdoc.org/d/seancorfield/next.jdbc/CURRENT/api/next.jdbc.date-time
@ -166,7 +166,7 @@
determine whether to call `.getObject` or some other method to read the determine whether to call `.getObject` or some other method to read the
column's value, and can choose whether or not to use the `ReadableColumn` column's value, and can choose whether or not to use the `ReadableColumn`
protocol-based value processor (and could add metadata to the value to protocol-based value processor (and could add metadata to the value to
satify that protocol on a per-instance basis)." satisfy that protocol on a per-instance basis)."
[builder-fn column-by-index-fn] [builder-fn column-by-index-fn]
(fn [rs opts] (fn [rs opts]
(let [builder (builder-fn rs opts)] (let [builder (builder-fn rs opts)]