If you rename a table or column today, ensync treats it as a drop and create/add. There's no way to perform an actual rename. I think this should be mainline functionality because of how common this need is during database development.
I picture having a [RenameFrom] attribute (that works both on classes and properties) that you would use temporarily for a merge to indicate what the prior name of something is before dropping it. Using this would inject an sp_rename call into the script.
If you rename a table or column today, ensync treats it as a drop and create/add. There's no way to perform an actual rename. I think this should be mainline functionality because of how common this need is during database development.
I picture having a
[RenameFrom]attribute (that works both on classes and properties) that you would use temporarily for a merge to indicate what the prior name of something is before dropping it. Using this would inject ansp_renamecall into the script.