Documentation:IsolationLevel: Difference between revisions

IsolationLevel

Latest revision as of 05:51, 20 January 2025

This page was created by Hans.karlsen@mdriven.net on 2022-04-24. Last edited by Edgar on 2025-01-20.

This is how a database tells how isolated a task is from other tasks in the database. See: https://docs.microsoft.com/en-us/dotnet/api/system.data.isolationlevel

In MDriven, set in SqlDatabaseConfig one isolation level for update UpdateIsolationLevel and one for read FetchIsolationLevel.

If you have too low a UpdateIsolationLevel extraction of new IDs and timestamps, it may not be unique and cause problems with your data integrity.

@@ Line 1: / Line 1: @@
-[https://docs.microsoft.com/en-us/dotnet/api/system.data.isolationlevel?view=net-6.0 https://docs.microsoft.com/en-us/dotnet/api/system.data.isolationlevel]
+<message>Write the content here to display this box</message>
+This is how a database tells how isolated a task is from other tasks in the database. See: [https://docs.microsoft.com/en-us/dotnet/api/system.data.isolationlevel?view=net-6.0 https://docs.microsoft.com/en-us/dotnet/api/system.data.isolationlevel]
-A database way to tell how isolated a task is from other tasks for the database.
+In MDriven, set in SqlDatabaseConfig one isolation level for update UpdateIsolationLevel and one for read FetchIsolationLevel.
-In MDriven you set in SqlDatabaseConfig one isolation level for update UpdateIsolationLevel and one for read FetchIsolationLevel.
+If you have too low a UpdateIsolationLevel extraction of new IDs and timestamps, it may not be unique and cause problems with your data integrity.
+[[Category:Database]]
-If you have a too low UpdateIsolationLevel extraction of new id's and timestamps my not be unique and cause problems with your data integrity
+{{Edited|July|12|2025}}