Originally created by @sunkehappy on GitHub (Oct 13, 2017).
I'm a MagicalRecord user. As we know it's been unmaintained for a long time. So I'm considering to switch a new library that is compatible with our existing code and that I could switch to step by step. It would be hard for me to remove MagicalRecord and add CoreStore in one step because it's highly coupled with my code.
So can anyone provide an migration guide for MagicalRecord user?
Originally created by @sunkehappy on GitHub (Oct 13, 2017).
I'm a [MagicalRecord](https://github.com/magicalpanda/MagicalRecord) user. As we know it's been unmaintained for a long time. So I'm considering to switch a new library that is compatible with our existing code and that I could switch to step by step. It would be hard for me to remove MagicalRecord and add CoreStore in one step because it's highly coupled with my code.
So can anyone provide an migration guide for MagicalRecord user?
Hi, I'm not sure what we could consider a "migration guide", because you would need to rewrite everything. You can use your xcdatamodeld files and NSManagedObject as is, but other than those I'm afraid you'd need to reimplement most of your existing code. (CoreStore for example enforces transaction paradigms, and hides away NSManagedObjectContexts)
You can refer to the README for how to implement common tasks.
@JohnEstropia commented on GitHub (Oct 14, 2017):
Hi, I'm not sure what we could consider a "migration guide", because you would need to rewrite everything. You can use your `xcdatamodeld` files and `NSManagedObject` as is, but other than those I'm afraid you'd need to reimplement most of your existing code. (CoreStore for example enforces transaction paradigms, and hides away `NSManagedObjectContext`s)
You can refer to the [README](https://github.com/JohnEstropia/CoreStore#contents) for how to implement common tasks.
That would be very hard for users like me to transfer from MagicalRecord to this project because it would take a long time to rewrite everything. That's too risky. I should think twice before take any action.
@sunkehappy commented on GitHub (Oct 16, 2017):
That would be very hard for users like me to transfer from MagicalRecord to this project because it would take a long time to rewrite everything. That's too risky. I should think twice before take any action.
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 @sunkehappy on GitHub (Oct 13, 2017).
I'm a MagicalRecord user. As we know it's been unmaintained for a long time. So I'm considering to switch a new library that is compatible with our existing code and that I could switch to step by step. It would be hard for me to remove MagicalRecord and add CoreStore in one step because it's highly coupled with my code.
So can anyone provide an migration guide for MagicalRecord user?
@JohnEstropia commented on GitHub (Oct 14, 2017):
Hi, I'm not sure what we could consider a "migration guide", because you would need to rewrite everything. You can use your
xcdatamodeldfiles andNSManagedObjectas is, but other than those I'm afraid you'd need to reimplement most of your existing code. (CoreStore for example enforces transaction paradigms, and hides awayNSManagedObjectContexts)You can refer to the README for how to implement common tasks.
@sunkehappy commented on GitHub (Oct 16, 2017):
That would be very hard for users like me to transfer from MagicalRecord to this project because it would take a long time to rewrite everything. That's too risky. I should think twice before take any action.