|
9 | 9 | - [Connecting to a Database](#connecting-to-a-database)
|
10 | 10 | - [Read-Write Databases](#read-write-databases)
|
11 | 11 | - [Read-Only Databases](#read-only-databases)
|
| 12 | + - [In a Shared Group Container](#in-a-shared-group-container) |
12 | 13 | - [In-Memory Databases](#in-memory-databases)
|
13 | 14 | - [URI parameters](#uri-parameters)
|
14 | 15 | - [Thread-Safety](#thread-safety)
|
@@ -173,7 +174,7 @@ See the [sqlite3 podspec][sqlite3pod] for more details.
|
173 | 174 | #### Using SQLite.swift with SQLCipher
|
174 | 175 |
|
175 | 176 | If you want to use [SQLCipher][] with SQLite.swift you can require the
|
176 |
| -`SQLCipher` subspec in your Podfile (SPM is not supported yet, see [#1084](/issues/1084)): |
| 177 | +`SQLCipher` subspec in your Podfile (SPM is not supported yet, see [#1084](https://github.com/stephencelis/SQLite.swift/issues/1084)): |
177 | 178 |
|
178 | 179 | ```ruby
|
179 | 180 | target 'YourAppTargetName' do
|
@@ -330,6 +331,13 @@ let db = try Connection(path, readonly: true)
|
330 | 331 | > We welcome changes to the above sample code to show how to successfully copy and use a bundled "seed"
|
331 | 332 | > database for writing in an app.
|
332 | 333 |
|
| 334 | +#### In a shared group container |
| 335 | + |
| 336 | +It is not recommend to store databases in a [shared group container], |
| 337 | +some users have reported crashes ([#1042](https://github.com/stephencelis/SQLite.swift/issues/1042)). |
| 338 | + |
| 339 | +[shared group container]: https://developer.apple.com/documentation/foundation/filemanager/1412643-containerurl# |
| 340 | + |
333 | 341 | #### In-Memory Databases
|
334 | 342 |
|
335 | 343 | If you omit the path, SQLite.swift will provision an [in-memory
|
|
0 commit comments