Merge branch 'feature/hashable' into develop

This commit is contained in:
2025-11-11 17:27:36 +02:00
5 changed files with 5 additions and 5 deletions

View File

@@ -7,7 +7,7 @@ extension Connection {
/// Two formats are supported:
/// - a passphrase, which undergoes key derivation;
/// - a raw 256-bit key (32 bytes) passed without transformation.
public enum Key {
public enum Key: Sendable {
/// A human-readable passphrase used for key derivation.
///
/// The passphrase is supplied as-is and processed by the underlying key derivation

View File

@@ -6,7 +6,7 @@ import Foundation
/// journal for rollback and recovery.
///
/// - SeeAlso: [journal_mode](https://sqlite.org/pragma.html#pragma_journal_mode)
public enum JournalMode: String, SQLiteRepresentable {
public enum JournalMode: String, SQLiteRepresentable, Sendable {
/// DELETE journal mode.
///
/// This is the default behavior. The rollback journal is deleted at the conclusion of each

View File

@@ -7,7 +7,7 @@ import Foundation
/// as the database name, table, and affected row ID.
///
/// - SeeAlso: [Data Change Notification Callbacks](https://sqlite.org/c3ref/update_hook.html)
public enum SQLiteAction {
public enum SQLiteAction: Hashable, Sendable {
/// A new row was inserted into a table.
///
/// - Parameters:

View File

@@ -6,7 +6,7 @@ import Foundation
/// disk. It defines the balance between durability, consistency, and performance during commits.
///
/// - SeeAlso: [PRAGMA synchronous](https://sqlite.org/pragma.html#pragma_synchronous)
public enum Synchronous: UInt8, SQLiteRepresentable {
public enum Synchronous: UInt8, SQLiteRepresentable, Sendable {
/// Disables synchronization for maximum performance.
///
/// With `synchronous=OFF`, SQLite does not wait for data to reach non-volatile storage before

View File

@@ -7,7 +7,7 @@ import Foundation
/// during the transaction.
///
/// - SeeAlso: [Transaction](https://sqlite.org/lang_transaction.html)
public enum TransactionType: String, CustomStringConvertible {
public enum TransactionType: String, CustomStringConvertible, Sendable {
/// Defers the start of the transaction until the first database access.
///
/// With `BEGIN DEFERRED`, no locks are acquired immediately. If the first statement is a read