Originally created by @JohnEstropia on GitHub (Jan 20, 2017).
(see NSManagedObjectContext.setQueryGenerationFromToken(.currentQueryGenerationToken))
Possible features:
Mark query generation tokens per transaction (no more faulting, possibly more efficient importing)
Potential for struct-based models (since data from snapshots are fixed)
Biggest potential: Dynamic entity model generation through reflection (use structs/non-NSManagedObject classes instead), plus complete independence from .xcdatamodeld files
Originally created by @JohnEstropia on GitHub (Jan 20, 2017).
(see `NSManagedObjectContext.setQueryGenerationFromToken(.currentQueryGenerationToken)`)
Possible features:
- Mark query generation tokens per transaction (no more faulting, possibly more efficient importing)
- Potential for struct-based models (since data from snapshots are fixed)
- Biggest potential: Dynamic entity model generation through reflection (use structs/non-NSManagedObject classes instead), plus complete independence from .xcdatamodeld files
Dynamic entity model generation through reflection (use structs/non-NSManagedObject classes instead), plus complete independence from .xcdatamodeld files
I'm closing this feature as it turns out Query Generations aren't that reliable (yet) and the struct-based models are memory hogs (no lazy properties)
@JohnEstropia commented on GitHub (Jul 23, 2017):
I'm closing this feature as it turns out Query Generations aren't that reliable (yet) and the struct-based models are memory hogs (no lazy properties)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @JohnEstropia on GitHub (Jan 20, 2017).
(see
NSManagedObjectContext.setQueryGenerationFromToken(.currentQueryGenerationToken))Possible features:
@JohnEstropia commented on GitHub (Jan 23, 2017):
Query Generations still looks iffy :( https://forums.developer.apple.com/message/186722#186722
Prioritize:
@JohnEstropia commented on GitHub (Jul 23, 2017):
I'm closing this feature as it turns out Query Generations aren't that reliable (yet) and the struct-based models are memory hogs (no lazy properties)