diff --git a/docs/configurations.mdx b/docs/configurations.mdx index fcdc1ffd..0a013d3f 100644 --- a/docs/configurations.mdx +++ b/docs/configurations.mdx @@ -101,7 +101,7 @@ Select a database to see the configurations available for each storage. If you're using SQLite3 as a JDBC database, you must set `scalar.db.contact_points` as follows: ```properties -scalar.db.contact_points=jdbc:sqlite:.sqlite3?busy_timeout=10000 +scalar.db.contact_points=jdbc:sqlite:?busy_timeout=10000 ``` Unlike other JDBC databases, [SQLite3 doesn't fully support concurrent access](https://www.sqlite.org/lang_transaction.html). To avoid frequent errors caused internally by [`SQLITE_BUSY`](https://www.sqlite.org/rescode.html#busy), setting a [`busy_timeout`](https://www.sqlite.org/c3ref/busy_timeout.html) parameter is recommended. diff --git a/docs/scalardb-cluster/scalardb-cluster-configurations.mdx b/docs/scalardb-cluster/scalardb-cluster-configurations.mdx index 74643a54..e8d172ec 100644 --- a/docs/scalardb-cluster/scalardb-cluster-configurations.mdx +++ b/docs/scalardb-cluster/scalardb-cluster-configurations.mdx @@ -118,7 +118,7 @@ Select a database to see the configurations available for each storage. If you're using SQLite3 as a JDBC database, you must set `scalar.db.contact_points` as follows: ```properties -scalar.db.contact_points=jdbc:sqlite:.sqlite3?busy_timeout=10000 +scalar.db.contact_points=jdbc:sqlite:?busy_timeout=10000 ``` Unlike other JDBC databases, [SQLite3 doesn't fully support concurrent access](https://www.sqlite.org/lang_transaction.html).