When transaction updating multiple records in the database, if one of the records does not exist, it leads to update failure. about grdb.swift HOT 4 CLOSED

@groue thank you very much

from grdb.swift.

Hello @songzhiming,

This is documented behavior, both in the README, and in the update method documentation. GRDB won't let your app think that an update was successful when nothing was actually updated.

If your app is OK with not updating anything, it has to be explicit, and catch this error:

do {
    try myRecord.update(db)
} catch RecordError.recordNotFound {
    // My record does not exist so we did not update anything.
    // This is OK because [insert your reason here].
}

from grdb.swift.

@groue
Are you suggesting that I catch only the "recordNotFound" error and continue to throw other errors?

from grdb.swift.

Yes indeed. That's the way, in Swift, to provide a specific handling for a specific error.

from grdb.swift.