From 8a5f0298cd18bfc6ec72956ec26a8ce210d2a7be Mon Sep 17 00:00:00 2001 From: Anders Murphy Date: Mon, 5 Sep 2022 19:25:44 +0100 Subject: [PATCH] Fix typo :repeatedable-read -> :repeatable-read --- doc/all-the-options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/all-the-options.md b/doc/all-the-options.md index c1e5a8d..f73b0ef 100644 --- a/doc/all-the-options.md +++ b/doc/all-the-options.md @@ -100,7 +100,7 @@ In addition to the above, `next.jdbc/execute-batch!` (which may create a `Prepar The `transact` function and `with-transaction` macro accept the following options: -* `:isolation` -- a keyword that identifies the isolation to be used for this transaction: `:none`, `:read-committed`, `:read-uncommitted`, `:repeatedable-read`, or `:serializable`; these represent increasingly strict levels of transaction isolation and may not all be available depending on the database and/or JDBC driver being used, +* `:isolation` -- a keyword that identifies the isolation to be used for this transaction: `:none`, `:read-committed`, `:read-uncommitted`, `:repeatable-read`, or `:serializable`; these represent increasingly strict levels of transaction isolation and may not all be available depending on the database and/or JDBC driver being used, * `:read-only` -- a `Boolean` that indicates whether the transaction should be read-only or not (the default), * `:rollback-only` -- a `Boolean` that indicates whether the transaction should commit on success (the default) or rollback.