The dirty checking is done by keeping the original JSON fetched from Postgresql and using Newtonsoft.Json to do a node by node comparison of the JSON representation of the document at the time that IDocumentSession is called. In the case an IDocumentSession opened with the dirty checking enabled, the session will try to detect changes to any of the documents loaded by that session. See identity for more information on document id's.
Anytime a document is registered through IDocumentSession.Store(document), Marten runs the "auto-assignment" policy for the id type of that document.
#IDOCUMENT 2 UPDATE#
The Postgresql functions generated by Marten to update the document storage tables perform "upserts" for you. The IServiceCollection.AddMarten() configuration will set up a DI registration for IQuerySession, so you can inject that into classes like this sample MVC controller:Ĭs public void using_identity_map () ĭo note that Marten's Store() method makes no distinctions between inserts and updates. While there are sections below describing each session in more detail, at a high level the different types of sessions are: Creationįor strictly read-only querying, the QuerySession is a lightweight session that is optimized for reading. iDocuments is AI solution for digitalizing engineering documents, including standards, specifications and datasheets.
The following diagram explains the relationship between the different flavors of session and the root store: IDocumentStore is the root of Marten usage, but most Marten usage in code will start with one of the session types that can be created from an IDocumentStore.
0 kommentar(er)
