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
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ The structure of the statements is influenced by the [SQLite Language Specificat
19
19
You will find an extensive usage of the composite pattern.
20
20
21
21
## How to use
22
-
If you want to let the Entity Framework create the database, if it does not exist, just set `SqliteDropCreateDatabaseAlways<>` or `SqliteCreateDatabaseIfNotExists` as your `IDbInitializer`.
22
+
If you want to let the Entity Framework create the database, if it does not exist, just set `SqliteDropCreateDatabaseAlways<>` or `SqliteCreateDatabaseIfNotExists<>` as your `IDbInitializer<>`.
23
23
```csharp
24
24
publicclassMyDbContext : DbContext
25
25
{
@@ -36,7 +36,7 @@ public class MyDbContext : DbContext
36
36
```
37
37
38
38
In a more advanced scenario you may want to populate some core- or test-data after the database was created.
39
-
To do this, inherit from `SqliteDropCreateDatabaseAlways<>` or `SqliteCreateDatabaseIfNotExists` and override the `Seed(MyDbContext context)` function.
39
+
To do this, inherit from `SqliteDropCreateDatabaseAlways<>` or `SqliteCreateDatabaseIfNotExists<>` and override the `Seed(MyDbContext context)` function.
40
40
This function will be called, in a own transaction, right after the database was created. This function is only executed if a new database was successfully created.
0 commit comments