Thank you for your feedback.
I would like to inform you that such code generation tool is indeed in our future plans and we plan to release it soon. We are going to announce it on the Telerik Blogs page
With regards to your schema migration questions - when Telerik Data Access
creates a migration script it also exposes description of the changes contained in that migration script so you could inspect those changes without the need of parsing the actual script.
This allows you to programically detect changes that you consider breaking or unsafe and react on that situation depending the exact case. For more information all the features exposed in the API please refer to this documentation article
In the referenced article, you will notice that the IsComplex()
method which return true
in case of structural changes in the script. This will detect columns that are to be dropped as well.
To utilize it, you can update the schema migration code on your side in similar way to the one shown below:
var info = schemaHandler.CreateUpdateInfo(
"Compldex schema changes detected. Please have a look"
script = schemaHandler.CreateUpdateDDLScript(
I would suggest you to play a bit with that API and come up with a set-up that matches your requirements. When a complex schema migration comes, you could manually inspect the script, making sure that it would indeed have the decried outcome or adjust the model accordingly.
I hope this helps. Do let us know if you have any further questions.
Check out the latest announcement
about Telerik Data Access vNext as a powerful framework
able to solve core development problems.