You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 800fc93
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,14 @@ The DAL infrastructure supports two execution models:
23
23
24
24
This allows individual DAL operations to run independently while also supporting coordinated operations across multiple DAL components within the same transaction.
25
25
26
+
## Database Migration Model
27
+
28
+
The migration framework is designed for application-integrated, forward-only database evolution. Migrations are registered explicitly in the order in which they must be applied, making the target schema deterministic and avoiding reflection-based discovery.
29
+
30
+
Applied migrations are stored as an ordered history. Before applying pending migrations, the framework validates that the stored history is an exact prefix of the configured migration sequence. This detects removed, renamed, reordered, or unknown migrations before any schema changes are made.
31
+
32
+
Transaction ownership is explicit and provider-controlled. A provider can execute the complete migration batch within its own transaction or participate in an existing database context, allowing migrations and application operations to share the same transaction.
33
+
26
34
## Commonly Used Types
27
35
28
36
-**`System.Data.DalBase<TDbContext>`**: Base class for DAL implementations that supports borrowed contexts and provider-managed owned context scopes.
// This file is used by Code Analysis to maintain SuppressMessage
2
+
// attributes that are applied to this project.
3
+
// Project-level suppressions either have no target or are given
4
+
// a specific target and scoped to a namespace, type, member, etc.
5
+
6
+
usingSystem.Diagnostics.CodeAnalysis;
7
+
8
+
[assembly:SuppressMessage("Style","IDE0130:Namespace does not match folder structure",Justification="<Pending>",Scope="namespace",Target="~N:System.Data.Tests")]
0 commit comments