Merge branch 'development'

Author: groue

.spi.yml

@@ -1,3 +1,4 @@
 version: 1
-external_links:
-  documentation: "https://github.com/groue/GRDB.swift/blob/master/README.md"
+builder:
+  configs:
+    - documentation_targets: [GRDB]

CHANGELOG.md

@@ -7,6 +7,7 @@ GRDB adheres to [Semantic Versioning](https://semver.org/), with one exception:
 
 #### 6.x Releases
 
+- `6.3.x` Releases - [6.3.0](#630)
 - `6.2.x` Releases - [6.2.0](#620)
 - `6.1.x` Releases - [6.1.0](#610)
 - `6.0.x` Releases - [6.0.0](#600)
@@ -100,6 +101,13 @@ GRDB adheres to [Semantic Versioning](https://semver.org/), with one exception:
 
 ---
 
+## 6.3.0
+
+Released November 6, 2022 • [diff](https://github.com/groue/GRDB.swift/compare/v6.2.0...v6.3.0)
+
+- **New**: [#1291](https://github.com/groue/GRDB.swift/pull/1291) by [@groue](https://github.com/groue): DocC inline documentation
+- **New**: The `Row.dataNoCopy` methods are deprecated. Use `Row.withUnsafeData` instead.
+
 ## 6.2.0
 
 Released October 28, 2022 • [diff](https://github.com/groue/GRDB.swift/compare/v6.1.0...v6.2.0)

CONTRIBUTING.md

@@ -69,7 +69,9 @@ How you can Contribute
 
 7. **Please provide documentation for your changes**
 
-    GRDB documentation is provided as reference (inline doc comments starting with `///`, see [Documentation Comment Syntax](https://github.com/apple/swift/blob/main/docs/DocumentationComments.md)), and guides ([README.md](README.md) and the [Documentation](Documentation) folder).
+    GRDB documentation is provided as a DocC reference, and guides ([README.md](README.md) and the [Documentation](Documentation) folder).
+    
+    Please keep the reference and the guides up-to-date. Use Xcode > Product > Build Documentation in order to control the quality of your reference documentation.
 
     GRDB is "documentation-driven", which means that nothing ships until it is supported by documentation that makes sense. Documentation makes sense when someone who is not you is able to figure out what is the purpose of your contribution, how to use it, and what are its eventual caveats and corner cases. When the documentation is hard to write, or reveals too many caveats, it is the sign that the api needs to be fixed.
 

Documentation/Concurrency.md

@@ -118,7 +118,7 @@ let playerCount = try dbQueue.read { db in
 }
 
 let newPlayerCount = try dbQueue.write { db -> Int in
-    try Player(id: 12, name: "Arthur").insert(db)
+    try Player(name: "Arthur").insert(db)
     return try Player.fetchCount(db)
 }
 ```
@@ -145,7 +145,7 @@ let playerCount = try await dbQueue.read { db in
 }
 
 let newPlayerCount = try await dbQueue.write { db -> Int in
-    try Player(id: 12, name: "Arthur").insert(db)
+    try Player(name: "Arthur").insert(db)
     return try Player.fetchCount(db)
 }
 ```
@@ -163,7 +163,7 @@ let playerCountPublisher = dbQueue.readPublisher { db in
 }
 
 let newPlayerCountPublisher = dbQueue.writePublisher { db -> Int in
-    try Player(id: 12, name: "Arthur").insert(db)
+    try Player(name: "Arthur").insert(db)
     return try Player.fetchCount(db)
 }
 ```
@@ -181,7 +181,7 @@ let playerCountObservable = dbQueue.rx.read { db in
 }
 
 let newPlayerCountObservable = dbQueue.rx.write { db -> Int in
-    try Player(id: 12, name: "Arthur").insert(db)
+    try Player(name: "Arthur").insert(db)
     return try Player.fetchCount(db)
 }
 ```
@@ -196,27 +196,24 @@ Those observables do not access the database until they are subscribed. They com
 ```swift
 dbQueue.asyncRead { (dbResult: Result<Database, Error>) in
     do {
-        // Maybe read access could not be established
         let db = try dbResult.get()
         let playerCount = try Player.fetchCount(db)
-        ... // Handle playerCount
     } catch {
-        ... // Handle error
+        // Handle error
     }
 }
 
-dbQueue.asyncWrite({ (db: Database) -> Int in
-    try Player(id: 12, name: "Arthur").insert(db)
+dbQueue.asyncWrite { (db: Database) -> Int in
+    try Player(name: "Arthur").insert(db)
     return try Player.fetchCount(db)
-}, completion: { (db: Database, result: Result<Int, Error>) in
-    // Handle write transaction result:
+} completion: { (db: Database, result: Result<Int, Error>) in
     switch result {
     case let .success(newPlayerCount):
-        ... // Handle newPlayerCount
+        // Handle success
     case let .failure(error):
-        ... // Handle error
+        // Handle error
     }
-})
+}
 ```
 
 </details>

Documentation/FullTextSearch.md

@@ -304,7 +304,7 @@ let pattern = FTS3Pattern(matchingAnyTokenIn: "")  // nil
 let pattern = FTS3Pattern(matchingAnyTokenIn: "*") // nil
 ```
 
-FTS3Pattern are regular [values](../README.md#values). You can use them as query [arguments](http://groue.github.io/GRDB.swift/docs/6.2/Structs/StatementArguments.html):
+FTS3Pattern are regular [values](../README.md#values). You can use them as query [arguments](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statementarguments):
 
 ```swift
 let documents = try Document.fetchAll(db,
@@ -587,7 +587,7 @@ let pattern = FTS5Pattern(matchingAnyTokenIn: "")  // nil
 let pattern = FTS5Pattern(matchingAnyTokenIn: "*") // nil
 ```
 
-FTS5Pattern are regular [values](../README.md#values). You can use them as query [arguments](http://groue.github.io/GRDB.swift/docs/6.2/Structs/StatementArguments.html):
+FTS5Pattern are regular [values](../README.md#values). You can use them as query [arguments](https://swiftpackageindex.com/groue/grdb/documentation/grdb/statementarguments):
 
 ```swift
 let documents = try Document.fetchAll(db,

Documentation/Migrations.md

@@ -77,7 +77,7 @@ try dbQueue.read { db in
 }
 ```
 
-See the [DatabaseMigrator reference](http://groue.github.io/GRDB.swift/docs/6.2/Structs/DatabaseMigrator.html) for more migrator methods.
+See the [DatabaseMigrator reference](https://swiftpackageindex.com/groue/grdb/documentation/grdb/databasemigrator) for more migrator methods.
 
 
 ## The `eraseDatabaseOnSchemaChange` Option

Documentation/ReleaseProcess.md

@@ -13,18 +13,14 @@ To release a new GRDB version:
 - On https://github.com/groue/sqlcipher.git upgrade, update SQLCipher version in README.md
 - On https://github.com/swiftlyfalling/SQLiteLib upgrade, update SQLite version in Documentation/CustomSQLiteBuilds.md
 - Update GRDB version number and release date in:
-    - Makefile
     - CHANGELOG.md
     - GRDB.swift.podspec
     - README.md
-    - Documentation/FullTextSearch.md
-    - Documentation/Migrations.md
     - Support/Info.plist
 - Commit and tag
 - Check tag authors: `git for-each-ref --format '%(refname) %(authorname)' refs/tags`
 - Push to the master & development branch
 - `pod trunk push --allow-warnings GRDB.swift.podspec`
-- `make doc`, and update index.html in the `gh-pages` branch
 - Update http://github.com/groue/WWDCCompanion
 - Update [performance comparison](https://github.com/groue/GRDB.swift/wiki/Performance):
 

GRDB.swift.podspec

@@ -1,6 +1,6 @@
 Pod::Spec.new do |s|
   s.name     = 'GRDB.swift'
-  s.version  = '6.2.0'
+  s.version  = '6.3.0'
 
   s.license  = { :type => 'MIT', :file => 'LICENSE' }
   s.summary  = 'A toolkit for SQLite databases, with a focus on application development.'