When I used to do Migrations, I always used ETL and then push to a dev system to review/test before going production.
The migration support is SwiftData is fine for a little tweak.
I might as well just just use new schema and context and write the custom code than use the SwiftData migration support.
And we are just supposed to know what ETL means?
My best guess is extract, transform, load.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Sorry, ETL is Extract (which means to pull the data from the source system to another system for mapping Transform: Transform the data Load: Push transformed data to the target system Typical migration method.
SwiftData migration does not follow this pattern.
