Releases: groue/GRDB.swift
Releases · groue/GRDB.swift
6.25.0
6.24.2
A new release of the Swift toolkit for SQLite databases.
- Documentation Update: #1485: The Sharing a Database guide was updated with a new recommendation for databases shared between multiple processes. Writers should always perform IMMEDIATE transactions in order to avoid the
SQLITE_BUSY
error that can occur when transactions overlap. The new recommendation fits in a single line of code:configuration.defaultTransactionKind = .immediate
. - New: Associations that involve views instead of tables were already supported, with an explicit
ForeignKey
in their definition. When the foreign key is missing, a clear diagnostic message is now emitted, instead of an unhelpful "no such table" runtime error.
Changes from 6.24.1 and 6.24.0:
- Fixed: #1477: Remove shadow tables from database dump
- New: #1466 by @barnettben: Add schema name option to database introspection methods
6.24.1
6.24.0
6.23.0
6.22.0
- New: #1452 by @groue: Bump SQLite custom builds to 3.44.0. Add support for FILTER and ORDER BY clauses in aggregate functions.
- New: #1460 by @groue: Explicit change notifications help applications deal with undetected database changes.
- Documentation Update: The documentations of
ValueObservation
,DatabaseRegionObservation
, andTransactionObserver
have a new "Dealing with Undetected Changes" section that documents possible strategies for notifying applications of undetected database changes.
6.21.0
6.20.2
6.20.1
6.19.0
- New: #1429 by @JhonnyBillM: Allow
DatabaseValueConvertible
types to customize their database JSON format - New: #1436 by @myyra and @groue: JSON functions
- New:
Database
has learned to create indexes on expressions, and specify specific collations on indexed columns, with thecreate(index:on:expressions:options:condition:)
method. - New: Codable records can specify coding strategies for their
Data
properties. See #1436 for more information. - Documentation Update: A new JSON Support article provides an overview of JSON handling.
- Documentation Update: The Recommended Practices for Designing Record Types now recommend that record types with an auto-incremented id avoid conforming to the
Identifiable
protocol.