We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For Core Data, there's an entire programming guide for data migration and versioning:
https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/CoreDataVersioning/Articles/Introduction.html#//apple_ref/doc/uid/TP40004399-CH1-SW1
Does hiberlite support any sort of data migration between schemas? What sort of approach should I take when (inevitably) the schema changes?
The text was updated successfully, but these errors were encountered:
I don't think this feature belongs into anything with a name *lite
*lite
Sorry, something went wrong.
Fair enough, but what does one do when the schema inevitably changes?
I'd go for the documentation of big frameworks and other links
Addition of fields and tables is handled automatically by hiberlite. Everything else you'd have to do using raw SQL.
No branches or pull requests
For Core Data, there's an entire programming guide for data migration and versioning:
https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/CoreDataVersioning/Articles/Introduction.html#//apple_ref/doc/uid/TP40004399-CH1-SW1
Does hiberlite support any sort of data migration between schemas? What sort of approach should I take when (inevitably) the schema changes?
The text was updated successfully, but these errors were encountered: