Is SQLiteData backed-up? Same as SwiftData on iCloud? #448
Replies: 2 comments 2 replies
-
|
Some where the Apple default zone is set to "co.pointfree.SQLiteData.defaultZone" I see it in the site: CloudKit - Records I'm wondering - I've NOT changed it... but should I change it to a more personal Zone Name"? |
Beta Was this translation helpful? Give feedback.
-
|
Oh... then - WHERE?? |
Beta Was this translation helpful? Give feedback.
-
That is the default zone we set here. You are free to change it, but if you have already saved records to that zone then changing the zone mess up the data (old data will live in one zone, new data in another). And there is no reason to change it. The most important thing is that you do not store anything in that zone yourself that was not done through SQLiteData.
We never claim to solve 100% of all problems related to persistence. Your user's data is stored in their iCloud account, and so I personally don't think the actual database file needs to be further backed up somewhere. But if you want to you can, but that is outside the purview of SQLiteData. You will have to figure out yourself how you want to do that. I am not familiar enough with how iCloud backups work to give any advice. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. David Koontz http://about.me/davidakoontzOn May 26, 2026, at 9:00 AM, Brandon Williams ***@***.***> wrote:
Some where the Apple default zone is set to "co.pointfree.SQLiteData.defaultZone" I see it in the site: CloudKit - Records
I'm wondering - I've NOT changed it... but should I change it to a more personal Zone Name"?
That is the default zone we set here. You are free to change it, but if you have already saved records to that zone then changing the zone mess up the data (old data will live in one zone, new data in another). And there is no reason to change it. The most important thing is that you do not store anything in that zone yourself that was not done through SQLiteData.
I've been watching your first series Modern Persistence - but it appears to jump right into the dev work. Leaving the mgmt/admin untouched... so far.
We never claim to solve 100% of all problems related to persistence. Your user's data is stored in their iCloud account, and so I personally don't think the actual database file needs to be further backed up somewhere. But if you want to you can, but that is outside the purview of SQLiteData. You will have to figure out yourself how you want to do that. I am not familiar enough with how iCloud backups work to give any advice.
—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I've swapped the DB for my App Portfolio Equity Curve. I've got some fixes yet to be made for items that were being presisted via the SwiftData Object Relationship Mapping (inherent saving -> SQL write() calls). But I've forgotten to ask... do I have to take on the role of a DB Admin and plan Back-ups, etc.?
My Interpretation: 1) Yes, Apple backs up your iPhone iPad device to iCloud and the Apps SwiftData DB or SQLiteData DB are part of the local device back-up.
My Interpretation: 2) Yes. I guess it is backed up... but where?
- There are Production & Development systems; Public, Private, Shared DB & Zones??
My Interpretation: 3) No.
I found Fatbobman's article helpful - but did not directly answer my questions.
Key Considerations Before Using SwiftData
https://fatbobman.com/en/posts/key-considerations-before-using-swiftdata/
I've been watching your first series Modern Persistence - but it appears to jump right into the dev work. Leaving the mgmt/admin untouched... so far.
David
Beta Was this translation helpful? Give feedback.
All reactions