swiftdata-pro

SwiftData Pro

Model, query, and persist data with SwiftData correctly and efficiently.

When to use

• Defining @Model types and relationships.
• Writing @Query / fetching in views.
• Setting up ModelContainer, migrations, or CloudKit sync.

Trigger: /swiftdata-pro.

Core principles

• @Model classes are reference types managed by a ModelContext.
• Inject the container at the app root with .modelContainer(for:).
• Read in views with @Query; write through the modelContext.
• Keep the main-actor context for UI; use a background ModelContext for bulk work.

Modeling

@Model
final class Trip {
    var name: String
    var startDate: Date
    @Relationship(deleteRule: .cascade) var stops: [Stop] = []

    init(name: String, startDate: Date) {
        self.name = name
        self.startDate = startDate
    }
}

• Set an explicit deleteRule on relationships — don't rely on defaults for ownership.
• Use @Attribute(.unique) for natural keys.
• Mark large blobs @Attribute(.externalStorage).

❌ No delete rule on an owning relationship

var stops: [Stop] = []   // orphans Stop rows when a Trip is deleted

✅

@Relationship(deleteRule: .cascade) var stops: [Stop] = []

Container setup

@main
struct TripsApp: App {
    var body: some Scene {
        WindowGroup { ContentView() }
            .modelContainer(for: Trip.self)
    }
}

Querying

Use @Query with sort/filter in the view; don't fetch-all then filter in Swift.

❌

@Query private var trips: [Trip]
var upcoming: [Trip] { trips.filter { $0.startDate > .now } }   // loads everything

✅

@Query(filter: #Predicate<Trip> { $0.startDate > Date.now },
       sort: \Trip.startDate)
private var upcoming: [Trip]

Writing

@Environment(\.modelContext) private var context

func add(_ trip: Trip) {
    context.insert(trip)
    // SwiftData autosaves; call try? context.save() only when you need it now.
}

Delete with context.delete(trip).