Idea: Built-in support for read-only stores #56

Open
opened 2025-12-29 15:23:15 +01:00 by adam · 0 comments
Owner

Originally created by @JohnEstropia on GitHub (May 9, 2016).

Originally assigned to: @JohnEstropia on GitHub.

Master-like objects that only ever gets read (and only gets written once, usually after app install) are common. The only reason people usually don't use Core Data for these is because it's ridiculously hard to maintain SQLite files. It may be useful if the data can be imported from an import file.

Test first if feasible. Features

  • completely read-only stack (except on initialization) (maybe a ReadOnlyDataStack)
  • import data on persistent store initialization by setting an import file
  • support several import file types (JSON, sqlite, XML maybe?)
  • just check changes in the import file then delete and recreate the store on app startup if needed.
Originally created by @JohnEstropia on GitHub (May 9, 2016). Originally assigned to: @JohnEstropia on GitHub. Master-like objects that only ever gets read (and only gets written once, usually after app install) are common. The only reason people usually don't use Core Data for these is because it's ridiculously hard to maintain SQLite files. It may be useful if the data can be imported from an import file. Test first if feasible. Features - [ ] completely read-only stack (except on initialization) (maybe a `ReadOnlyDataStack`) - [ ] import data on persistent store initialization by setting an import file - [ ] support several import file types (JSON, sqlite, XML maybe?) - [ ] just check changes in the import file then delete and recreate the store on app startup if needed.
adam added the enhancement label 2025-12-29 15:23:15 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/CoreStore#56