NPersist Feature Guide:

Persistence to Xml documents

In addition to persisting to relational databases, NPersist supports persistence to xml documents saved as files on the hard drive. This can be useful for reasonably sized datasets that are naturally hierarchical and (preferably) where the state isn’t overly shared between users. An example could be custom application configuration files or an RSS reader saving local copies of feeds as xml to disk.

While there are limitations to this approach – for example, objects have to be read into memory before they can be queried, meaning the approach doesn’t work well with datasets that do not fit comfortably in memory and can be loaded from disk in reasonable times – the objects will still enjoy the full fledged runtime support that NPersist offers.

That means that your objects will be dirty tracked, have their inverse properties managed, will keep copies of their original values etc. This would be the primary reason for using NPersist for working with graphs that are saved to xml rather than just working directly with xml access APIs.

NPersist supports that you save your objects to one big file or to multiple files. Using multiple files, you can use one file per class, one file per object or one file per object hierarchy. You can also mix all these approaches.

Last edited Feb 23, 2008 at 4:15 AM by matshelander, version 1


No comments yet.