dbManager.Update does not respect [MagicNotMapped] attribute

[bitzblitz]

After I call Update on an existing element in the database it updates with ALL fields, which messes up my data. When the record was originally saved my [MagicNotMapped] fields were not included in the records.

[yueyinqiu]

It seems like in Update we forgot MagicNotMapped at all. Maybe also for encryption? I will check that as soon as possible. The relevant code is a bit messy. Maybe a great refactor is needed.

[magiccodingman]

This bug is being resolved in this PR:
#38

will merge in changes and close it out after @yueyinqiu has time to check my back.

[magiccodingman]

#43
This not only further resolves this, but has massive performance improvements within the completely overhauled serialization system. Closing this and will put out a release when the finalized version is posted to NuGet. Just making sure all kinks are worked out prior to the next release as the refactor was so massive that it needs significant testing.

Closing this ticket. Please be advised to watch release status.