I cant find a clean task that removes “dead” properties in the data due to schema changes.
In 4.7 this happened when you saved a document.
Would be nice to have this as a Toolbox CLI task or that it does this when saving a document.
4 Likes
I think this might come from the fact that the data is in reality schemaless, even though we defined them in a content type, etc.? (ref NoSQL vs relational databases)
But I would like to be able to define upgrade-scripts that run when you upgrade an app. That way we can have full control, and also convert old data to new schemas. (Not just remove data that no longer matches the new schema)
I am looking for this in an app I am developing. I already know the next version will not be backwards-compatible, but I don’t want to skip releasing the current version. If I can’t upgrade the data, it will be impossible to upgrade the app, and I would probably need to create a completely new app.
Taking this one step further, scheduled jobs configured in the apps would be great. Being able to specify jobs that run when starting an app, at certain times each day/week/month/year, etc. is really useful.
Yes, we can do that by running native batch-jobs on the server, but that does not work if it is important for an app in the marketplace, as it should be able to work without doing more than installing it.
2 Likes
We are thinking about how to make the upgrade better. And we have a scriptable upgrade for apps on the drawing-board.
3 Likes
Hmm… Are you basically saying removed properties from old content types are not cleaned up when editing and saving the document with a new content type?
2 Likes