SQLite-backed durable session and message stores for the Pulse MQTT client: subscriptions, the offline queue, and in-flight QoS state survive restarts. Hand-written SQL, AOT-safe, no reflection ORM.
Dynamic Object Relational Mapping technology for easy CRUD operations
A specification library for Rochas.DapperRepository implementation
Run SQL on any ADO.NET connection and get the rows back as strongly typed objects (ExecuteQuery<T>, ExecuteQueryAsync<T>) or as dynamic objects (ExecuteQuery, ExecuteQueryAsync), streamed as IEnumerable<T> or IAsyncEnumerable<T>. The methods extend DbConnection and DbCommand; ExecuteCommand and ExecuteCommandAsync run statements that return no rows. An error the database raises after the rows (SQL Server THROW after a SELECT) is thrown when the rows are read to their end. Parameters are written as {{name}} in the SQL and always sent as real database parameters, never concatenated into it. Their names can hold any characters, so a JSON body's keys work as they are ({{first name}}, {{e-mail}}); names are matched ignoring case, and a name the parameters object lacks, or whose value is null, is sent as NULL. Their values come from an anonymous object, a dictionary, a JsonElement or JSON text, and the delimiters can be changed. Several parameter sources, each with its own delimiters, can fill one query, a later source taking precedence. Typed results map columns to properties by name, or by [DataMember] or [JsonPropertyName]. JSON and XML columns can be returned as nested objects. Works with SQL Server, PostgreSQL, MySQL and MariaDB, SQLite, Oracle, DB2 and any other ADO.NET provider; on ODBC and OleDb the named parameters become positional ? parameters automatically. No package dependencies on .NET 8 and later. Targets .NET 11, 10, 9 and 8, and .NET Standard 2.0, which includes .NET Framework 4.6.1 and later.
SQLite Provider for SimpleStack.Orm based on System.Data.Sqlite
IDbTransaction extension methods for Dapper: A high performance Micro-ORM supporting SQL Server, MySQL, Sqlite, SqlCE, Firebird etc.. --------------------------------------- This library is sponsored by ZZZ Projects: https://dapper-plus.net/ https://eval-expression.net/ https://entityframework-extensions.net/ ---------------------------------------
Incredibly easy and talented micro orm library for SQLite
FluentData.Core is a Micro ORM that makes it simple to select, insert, update and delete data in a database. It gives the developer the power of ADO.NET but with the convenience of an ORM. It has a simple to use fluent API that uses SQL - the best and most suitable language to query data, and SQL or fluent builders to insert, update and delete data.
SinGooCMS.Ado 支持netstandard2.1和net framework 4.6.1,原生sql语句操作,支持SqlServer、MySql、Sqlite、Oracle
NLite.Data Framework 是一个轻量简单易用的开源Linq ORM数据访问组件,支持Nullable类型和枚举类型,对Linq的谓词提供了完美的支持,旨在让绝大部份的主流数据库都使用 Linq 来进行程序开发,让开发人员访问数据库从SQL中解放出来,易学易用上手快,配置简单,并且提供了源代码下载,方便定制。支持多数据库,目前支持Access、SQLServer、SqlCE、SQLite、MySQL、ORACLE,未来还会支持更多的数据库。 设计理念 一: 约定胜于配置 连接字符串的配置完全遵循.Net 的连接字符串配置规范。 表名映射原则: 默认情况下表名和实体类名完全一致,如果不一致那么可以通过TableAttribute标签来制定,下个版本或许将会增加其它的扩展方式 列名映射原则:默认情况下实体的属性或字段和表中列名完全一致(不区分大小写),如果不一致那么可以通过ColumnAttribute标签来制定,下个版本或许将会增加其它的扩展方式 单一主键映射原则:默认情况下实体的ID属性或”实体名称"+ID的属性自动映射为表的主键,当字段或属性的类型是Int型或Long类型时,那么该字段在数据库中应是自动增一或基于序列的方式 多主键映射原则:如果表中有联合主键那么需要在是实体类中把对应的字段或属性添加IdAttribute标签即可 一对多映射原则:假设有两个实体Customer 和 Order两个实体,Customer 里面包含一个Order的列表属性,那么只需要在Order类里面包含一个CustomerID 的属性或字段即可自动完成一对多映射,当然也可以通过AssociationAttribute标签来指定映射的ThisKey 和ThatKey来手动建立关联(建议自动建立)。 多对一映射原则:假设有两个实体Customer 和 Order两个实体,Order里面包含一个Customer的属性引用,那么只需要在Order类里面包含一个CustomerID 的属性或字段即可自动完成一对多映射,当然也可以通过AssociationAttribute标签来指定映射的ThisKey 和ThatKey来手动建立关联(建议自动建立),其实一对多和多对一的映射完全一致都需要在多方的那里添加一个属性(一方的类名名称+“ID”)。 多对多映射原则:不支持,需要转换成两个一对多映射,和数据库完全保持一致. 二:基于关系的OR映射的原则 表和实体是一一对应的,不支持多对多,完全遵循数据库的设计规范,降低开发人员的学习成本(因为数据库不支持多对多,如果OR映射支持多对多那么开发人员将要学习多对多的映射规则,比如NHibernate,ManyToMany、Set、Bag、Reverse等配置规范以及在多对对数据保存的时候也需要很多学习成本) 三:无状态原则 DbContext中没有保存实体的状态,没有任何数据缓存,所有的数据都是和数据库实时的,只要调用DbSet的Insert、Update、Save方法将立即和数据库进行对应的操作。
A high performance Micro-ORM supporting SQL Server, MySQL, Sqlite, SqlCE, Firebird etc..
DbHelper is a modern object-relational mapper (O/RM) for .NET. It supports updates, and schema migrations. DbHelper works with SQL Server, SQLite, MySQL, PostgreSQL, and Oracle through a provider plugin API.
SQL provider implementations for OmniDataAccess (PostgreSQL, CockroachDB, MySQL, SQL Server, SQLite) plus the OmniDB ORM layer. Includes an async-first ADO.NET-style manager (ISqlDatabaseManager) with mapped queries, streaming, paging, entity CRUD, bulk operations, transactions with savepoints, and stored procedures — and a higher-level entity API with a fluent LINQ query builder, eager loading, soft delete, optimistic concurrency, schema generation, and migrations.
SQLite Helper is an open source .NETStandard library for easy storage and access of data from SQLite databases. It uses SQLitePCLRaw to provide platform independent access to sqlite. !!WARNING!! Library is currently in beta, breaking changes might occur!!
Solve SQLite concurrency errors (SQLITE_BUSY, "database is locked", SQLITE_BUSY_SNAPSHOT) in Entity Framework Core with drop-in write serialization. Implements Channel-based queuing, automatic BEGIN IMMEDIATE transaction upgrades, exponential-backoff retry with full jitter, WAL-mode optimization, and 10x faster bulk inserts. Solves multi-writer, multi-reader conflicts without connection pooling complexity. Works with .NET 10 and netstandard 2.0 runtimes. Security: Updated SQLitePCLRaw.core to 2.1.12 (fixes GHSA-2m69-gcr7-jv3q).
Lightweight ActiveRecord-inspired ORM for .NET, Windows Phone and Mono(Touch/Droid)
NOT ORM, but simple & portable .NET Data Access library for SQL Server, MySQL, PostgreSQL, SQLite.
Dapper is a Stack Overflow ORM Framewrok , now I supported to Migrations for PgSQL,MSSQL,MySQL and by default SQLlite.
A hybrid .NET ORM library for SQLite (using System.Data.SQLite.Core).
Interactive global .NET tool (efvibe) to run LINQ against an external project's EF Core DbContext with most relational providers (SQL Server, PostgreSQL, SQLite, Oracle, MySQL, Firebird, and more), plus SQL, query plans, and session analytics.
A hybrid .NET ORM library for SQLite (using System.Data.SQLite.Core).
SQLite support for DataLinq - a lightweight, high-performance .NET ORM using source generators for immutability and efficient caching - optimized for read-heavy applications.
A high performance Micro-ORM supporting Sql Server, MySQL, Sqlite, SqlCE, Firebird etc..
OSX .NET Core Sqlite runtime libraries for Iridium
Linux .NET Core Sqlite runtime libraries for Iridium
.NET's best ORM data layer framework, one of the wood, low-key continuous update for 15 years! In the tank. Net Framework 2.0+, supported. Net Core 2.1+ supports a variety of databases, built-in database read/write separation, distributed cache, distributed locks, etc(.Net 最好用的ORM数据层框架,木有之一,低调持续更新15年!支持.Net Framework 2.0+,支持.Net Core 2.1+,支持多种数据库,自带数据库读写分离,分布式缓存,分布式锁等,开源地址:https://github.com/cyq1162/cyqdata)
SQLite-Net Extensions is a very simple ORM that provides one-to-one, one-to-many, many-to-one, many-to-many, inverse and text-blobbed relationships on top of the sqlite-net library. This package update sqlite-net-pcl version,because old version has bug in xamarin.android
.NET's best ORM data layer framework, one of the wood, low-key continuous update for 15 years! In the tank. Net Framework 2.0+, supported. Net Core 2.1+ supports a variety of databases, built-in database read/write separation, distributed cache, distributed locks, etc(.Net 最好用的ORM数据层框架,木有之一,低调持续更新15年!支持.Net Framework 2.0+,支持.Net Core 2.1+,支持多种数据库,自带数据库读写分离,分布式缓存,分布式锁等,开源地址:https://github.com/cyq1162/cyqdata)