LiteDB icon indicating copy to clipboard operation
LiteDB copied to clipboard

How to future-proof database/avoid migration with version changes?

Open devmaestro1 opened this issue 3 years ago • 0 comments

Hello,

I am wondering what is the best approach to ensure that I minimize the necessity of database migrations as my code changes. In particular, I note that LiteDB stores the fully-qualified class name along with the version number. Does this mean that if I increment my assembly version number I will break existing data? If so, is there any way around this so it uses only the class name and not version (etc)?

Thanks.

devmaestro1 avatar May 06 '22 05:05 devmaestro1