Core

The provider-agnostic CRUD and aggregate operations every database provider builds on — the foundation of RepoDB as a Productivity Platform, not just an ORM.

RepoDB has grown from a hybrid ORM into a full Productivity Platform for working with data access in .NET — Quickstart to get running against your database, Features for the capabilities layered on top (caching, bulk operations, tracing, telemetry, and more), and Operations for the exact method-level reference you’re looking at now. Core is the foundation all of that sits on: the same provider-agnostic set of operations every one of RepoDB’s database providers implements identically, so the platform behaves the same way whether you’re on SQL Server, PostgreSQL, or SQLite.

What’s included

These are the provider-agnostic CRUD and aggregate operations available on every supported RDBMS. They cover fetching data (Query, QueryAll, BatchQuery, QueryMultiple), writing data (Insert, InsertAll, Update, UpdateAll, Merge, MergeAll, Delete, DeleteAll), row/table introspection (Count, CountAll, Exists, Truncate), aggregation (Average, AverageAll, Max, MaxAll, Min, MinAll, Sum, SumAll), and raw-SQL execution (ExecuteQuery, ExecuteQueryMultiple, ExecuteReader, ExecuteNonQuery, ExecuteScalar). Each operation has both a synchronous and an Async counterpart.

Where Core fits

Every database provider — SQL Server, PostgreSQL, MySQL, and the rest — implements this exact same set of operations, which is what lets application code move between providers with minimal changes. Providers then extend Core with their own native capabilities, most visibly bulk operations (BulkInsert, BulkMerge, BulkUpdate, BulkDelete), listed under each provider’s own group in the sidebar. Platform-level capabilities that cut across all of it — caching, tracing, telemetry, property handlers, and more — are documented under Features, and each package’s version history lives under Releases.