So, if I change entity's namespace, then PerformSafely silently succeeds: there are no unsafe actions. But if there is actual data in the entity any ugrade will fail, since DO tries to delete all data from the moved entity.

For example. Move an entity Test.EnNodeShape -> Test2.EnNodeShape This will result in this SQL during upgrade:

DELETE FROM [dbo].[EnNodeShape];

Which is actually unacceptable. Luckily the workaround is to add a RenameTypeHint.

I suppose there must be an unsafeaction during upgrade or proper NS change handling

asked Apr 03 '13 at 06:45

xumix's gravatar image


Thanks for the report, problem is confirmed, we've sent combat robots to punish authors of this bug :-)

(Apr 09 '13 at 04:02) Denis Krjuchkov Denis%20Krjuchkov's gravatar image

One Answer:

Hello xumix,

fix would be available in DataObjects.Net 4.5.8/4.6.4

Namespace-only renames (more precisely renames that don't change TypeInfo.Name) would be automatically tracked and processed without additional hints.

answered Jul 18 '13 at 09:55

Denis%20Krjuchkov's gravatar image

Denis Krjuchkov

Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview

powered by OSQA