at the moment, we don't have any active provisions that could guard you against these kind of changes in your model. What you can do is to turn off database update (that can't detect field and class renamings), generate the DDL script through Database.GetSchemaHandler().CreateUpdateDDLScript(), review it and execute it programmatically by ExecuteDDLScript(). The same content is also stored in a file in the output directory, so that you can review it later, or generate a combined script that can then be applied to your production database. This assumes that you are not directly working against your production database, but modify a developer's version and that you are using 'forward' mapping (class->table)
We are in the process of defining a better, likely more fail-safe approach for these kind of operations for a future version. Your input is very welcome!
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items