Net4x.DapperLibrary.InMemory 1.9.9.8

DapperLibrary.InMemory

Provides a lightweight in-memory SQLite IDapperContext implementation intended for tests and scenarios where a transient, fast database instance is useful.

Overview

• Main type: InMemoryDapperContext (inherits from SQLiteDapperContext).
• Purpose: expose an in-memory SQLite connection (shared cache) that can be used for unit/integration tests without creating files on disk.
• Default connection string: Data Source=InMemory;Mode=Memory;Cache=Shared.
• Provider: the context uses the ADO.NET SQLite provider (the code references System.Data.SQLite).

Usage

Create and use a context directly:

using var context = new InMemoryDapperContext();
// use context.Operations / context.Schema / context.SaveDataTable etc.

Register the context creator so other code that uses the global factory receives an in-memory context:

// register a context creator with DapperContextFactory
InMemoryDapperContext.Use();

// later, callers using DapperContextFactory.Instance.CreateContext() will receive an in-memory context

Notes:

• The in-memory database uses SQLite's memory mode with Cache=Shared, so multiple connections using the same connection string will share the same in-memory database within the process.
• This is ideal for unit tests where you need predictable, fast, temporary persistence.

Implementation details

• The static Use() method registers a context creator in the DapperContextFactory using a DapperConnectionStringSettings configured with the in-memory connection string and the SQLite provider name.
• Constructing InMemoryDapperContext directly will initialize the base SQLiteDapperContext with the in-memory settings.

Recommendations

• For tests that require isolation between test cases, ensure the in-memory database is reset between tests (e.g., by disposing contexts and recreating schema).
• If you need file-backed persistence or provider-specific behavior (e.g., different SQL dialects), use the appropriate provider-specific context (SQLite file, SQL Server, Postgres, etc.).

License / Contributing

See repository root for license and contribution guidelines.