Currently that's not the case because Sterling doesn't save a "table" but relies on the active type definition. Eventually that will be the route to go but unfortunately it's not yet available. Currently, Sterling has an algorithm to inspect properties and
fields on the type, and then parses the stream based on those properties and fields. If you add a new property, it will expect additional data that doesn't exist.
Obviously the fix will be to serialize the list of properties in the table information and parse based on that, but then there are additional nuances such as when properties drop off or require defaults, etc, so it hasn't been addressed yet.
I'll try to figure out why the link is broken, but in essence the reference does this:
Then if I need to revise it, I'll do:
Class name can stay the same, etc, and then I just detect if I've upgraded yet. If not, I have a special class that works in both namespaces, reads from the old and writes to the new.
Probably eventually will be able to take something that simply inspects the stream and rebuilds the types as well - I've been toying with the idea of an out of browser "inspector" for Sterling like a SQL console but just haven't had bandwidth yet to delve
I know upgrade is not a good story now, but will be focusing on some good solutions for it down the road.