shiny-documentdb

To store JSON documents in a .NET app without a rigid relational schema, you can use a schema-free document store that bridges relational data and JSON storage. This enables type-safe persistence and LINQ querying across multiple database providers without defining fixed tables.

Yes, you can use LINQ to query JSON document storage across SQLite, MySQL, and PostgreSQL. A provider-agnostic setup with MapTypeToTable and DI extensions allows you to switch databases without changing code, ensuring consistent querying behavior across providers.

The best way to configure a multi-provider document store in .NET is by using provider abstractions and DI extensions. You instantiate a DocumentStore with your chosen provider, map domain types with MapTypeToTable, and use custom Id properties for consistent cross-database behavior.

Yes, this .NET document store supports full AOT compilation and trimming. It uses AOT-ready serialization for JSON projections, ensuring the schema-free persistence layer remains compatible with ahead-of-time compilation requirements in .NET applications.

To set up custom Id properties and type mapping for a .NET JSON document store, you use MapTypeToTable during configuration. This maps your domain types to the underlying storage while allowing custom Id properties to ensure consistent document identification across SQLite, SQLCipher, MySQL, SQL Server, and PostgreSQL.