Published:
We just announced preview support for ClickHouse — read that first if you haven’t yet. This post goes one level deeper: how RepoDb.ClickHouse and RepoDb.ClickHouse.BulkOperations are built, why ClickHouse needed more than a drop-in provider swap, and enough code to get productive with it right away.
Published:
We just announced RepoDB Connectors, a new home for dedicated, provider-specific ADO.NET data providers built for RepoDB — read the announcement at Introducing RepoDB Connectors — Starting with MariaDB if you haven’t yet. This post goes one level deeper into the first connector that shipped out of it, RepoDb.Connector.MariaDb: why it exists, how it’s laid out internally, the objects it exposes, and enough code to get productive with it right away.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
We just announced preview support for ClickHouse — read that first if you haven’t yet. This post goes one level deeper: how RepoDb.ClickHouse and RepoDb.ClickHouse.BulkOperations are built, why ClickHouse needed more than a drop-in provider swap, and enough code to get productive with it right away.
Published:
RepoDB has grown from a single hybrid-ORM library into a small family of packages — connectors, bulk operations, and now RepoDB Insights. It’s a good point to step back and lay out how all of it fits together. The diagram below is the mental model going forward, and this post walks through every box and the connections between them.
Published:
We just announced RepoDB Connectors, a new home for dedicated, provider-specific ADO.NET data providers built for RepoDB — read the announcement at Introducing RepoDB Connectors — Starting with MariaDB if you haven’t yet. This post goes one level deeper into the first connector that shipped out of it, RepoDb.Connector.MariaDb: why it exists, how it’s laid out internally, the objects it exposes, and enough code to get productive with it right away.
Published:
We just announced preview support for ClickHouse — read that first if you haven’t yet. This post goes one level deeper: how RepoDb.ClickHouse and RepoDb.ClickHouse.BulkOperations are built, why ClickHouse needed more than a drop-in provider swap, and enough code to get productive with it right away.
Published:
Even RepoDB is not just another ORM anymore, what started as a Dapper-shaped micro-ORM has grown into a layered platform — see RepoDB’s New Architecture — with its own provider-specific connectors, high-throughput Bulk/Batch operations, and an Insights stack for telemetry sitting above the same core CRUD surface. None of that changes the migration path below — the CRUD layer this post covers is still the part that talks to IDbConnection the same way Dapper does — but it’s worth knowing upfront that migrating gets you a foundation to grow into, not just a like-for-like swap.
Published:
RepoDB has grown from a single hybrid-ORM library into a small family of packages — connectors, bulk operations, and now RepoDB Insights. It’s a good point to step back and lay out how all of it fits together. The diagram below is the mental model going forward, and this post walks through every box and the connections between them.
Published:
We just announced RepoDB Connectors, a new home for dedicated, provider-specific ADO.NET data providers built for RepoDB — read the announcement at Introducing RepoDB Connectors — Starting with MariaDB if you haven’t yet. This post goes one level deeper into the first connector that shipped out of it, RepoDb.Connector.MariaDb: why it exists, how it’s laid out internally, the objects it exposes, and enough code to get productive with it right away.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
We are very excited to announce the availability of the PropertyValueAttribute object. It enables you (as a user of the library) to set the property of the IDbDataParameter object before the actual execution against the database.
Published:
Today, we are announcing the availability of RepoDb v1.12.5 and its bundles, the extension libraries at >= v1.1.2. See below.
Published:
When we announced the GA of RepoDB v1.12.0, many users were not able to pre-test the solutions even by having the 4 betas for the last 2 months. This has unfortunately led them to file the issues/bugs right after the releases.
Published:
Today, we are announcing the complete support of RepoDB for the CancellationToken.
Published:
Today, we are announcing the availability of RepoDb v1.12.0. The released packages also come with their bundles, the extension libraries at v1.1.0. See below.
Published:
In this page, we will share with you the differences and what sets RepoDB apart from Dapper. We tried our best to make a 1-to-1 comparison for most areas. This page will hopefully help you decide as a developer to choose RepoDB as your micro-ORM (with a compelling reason).
Published:
We would like to share with you the latest and greatest updates of RepoDB ORM. Recently, we just published the complete out-of-the-box support of Bulk Operations for SQL Server in .NET data access space.
Published:
It was 2 years ago when the first version release of RepoDB was placed at Nuget.org.
Published:
As of writing this, I am busy working on the RepoDB.NET site, providing content to each page.
Published:
We just announced preview support for ClickHouse — read that first if you haven’t yet. This post goes one level deeper: how RepoDb.ClickHouse and RepoDb.ClickHouse.BulkOperations are built, why ClickHouse needed more than a drop-in provider swap, and enough code to get productive with it right away.
Published:
We just announced RepoDB Connectors, a new home for dedicated, provider-specific ADO.NET data providers built for RepoDB — read the announcement at Introducing RepoDB Connectors — Starting with MariaDB if you haven’t yet. This post goes one level deeper into the first connector that shipped out of it, RepoDb.Connector.MariaDb: why it exists, how it’s laid out internally, the objects it exposes, and enough code to get productive with it right away.
Published:
We just announced preview support for ClickHouse — read that first if you haven’t yet. This post goes one level deeper: how RepoDb.ClickHouse and RepoDb.ClickHouse.BulkOperations are built, why ClickHouse needed more than a drop-in provider swap, and enough code to get productive with it right away.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
RepoDB has grown from a single hybrid-ORM library into a small family of packages — connectors, bulk operations, and now RepoDB Insights. It’s a good point to step back and lay out how all of it fits together. The diagram below is the mental model going forward, and this post walks through every box and the connections between them.
Published:
We just announced RepoDB Connectors, a new home for dedicated, provider-specific ADO.NET data providers built for RepoDB — read the announcement at Introducing RepoDB Connectors — Starting with MariaDB if you haven’t yet. This post goes one level deeper into the first connector that shipped out of it, RepoDb.Connector.MariaDb: why it exists, how it’s laid out internally, the objects it exposes, and enough code to get productive with it right away.
Published:
Even RepoDB is not just another ORM anymore, what started as a Dapper-shaped micro-ORM has grown into a layered platform — see RepoDB’s New Architecture — with its own provider-specific connectors, high-throughput Bulk/Batch operations, and an Insights stack for telemetry sitting above the same core CRUD surface. None of that changes the migration path below — the CRUD layer this post covers is still the part that talks to IDbConnection the same way Dapper does — but it’s worth knowing upfront that migrating gets you a foundation to grow into, not just a like-for-like swap.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
RepoDB has grown from a single hybrid-ORM library into a small family of packages — connectors, bulk operations, and now RepoDB Insights. It’s a good point to step back and lay out how all of it fits together. The diagram below is the mental model going forward, and this post walks through every box and the connections between them.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
We just announced RepoDB Connectors, a new home for dedicated, provider-specific ADO.NET data providers built for RepoDB — read the announcement at Introducing RepoDB Connectors — Starting with MariaDB if you haven’t yet. This post goes one level deeper into the first connector that shipped out of it, RepoDb.Connector.MariaDb: why it exists, how it’s laid out internally, the objects it exposes, and enough code to get productive with it right away.
Published:
Even RepoDB is not just another ORM anymore, what started as a Dapper-shaped micro-ORM has grown into a layered platform — see RepoDB’s New Architecture — with its own provider-specific connectors, high-throughput Bulk/Batch operations, and an Insights stack for telemetry sitting above the same core CRUD surface. None of that changes the migration path below — the CRUD layer this post covers is still the part that talks to IDbConnection the same way Dapper does — but it’s worth knowing upfront that migrating gets you a foundation to grow into, not just a like-for-like swap.
Published:
Even RepoDB is not just another ORM anymore, what started as a Dapper-shaped micro-ORM has grown into a layered platform — see RepoDB’s New Architecture — with its own provider-specific connectors, high-throughput Bulk/Batch operations, and an Insights stack for telemetry sitting above the same core CRUD surface. None of that changes the migration path below — the CRUD layer this post covers is still the part that talks to IDbConnection the same way Dapper does — but it’s worth knowing upfront that migrating gets you a foundation to grow into, not just a like-for-like swap.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
We just announced preview support for ClickHouse — read that first if you haven’t yet. This post goes one level deeper: how RepoDb.ClickHouse and RepoDb.ClickHouse.BulkOperations are built, why ClickHouse needed more than a drop-in provider swap, and enough code to get productive with it right away.
Published:
We just announced RepoDB Connectors, a new home for dedicated, provider-specific ADO.NET data providers built for RepoDB — read the announcement at Introducing RepoDB Connectors — Starting with MariaDB if you haven’t yet. This post goes one level deeper into the first connector that shipped out of it, RepoDb.Connector.MariaDb: why it exists, how it’s laid out internally, the objects it exposes, and enough code to get productive with it right away.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
We just announced preview support for ClickHouse — read that first if you haven’t yet. This post goes one level deeper: how RepoDb.ClickHouse and RepoDb.ClickHouse.BulkOperations are built, why ClickHouse needed more than a drop-in provider swap, and enough code to get productive with it right away.
Published:
Even RepoDB is not just another ORM anymore, what started as a Dapper-shaped micro-ORM has grown into a layered platform — see RepoDB’s New Architecture — with its own provider-specific connectors, high-throughput Bulk/Batch operations, and an Insights stack for telemetry sitting above the same core CRUD surface. None of that changes the migration path below — the CRUD layer this post covers is still the part that talks to IDbConnection the same way Dapper does — but it’s worth knowing upfront that migrating gets you a foundation to grow into, not just a like-for-like swap.
Published:
RepoDB has grown from a single hybrid-ORM library into a small family of packages — connectors, bulk operations, and now RepoDB Insights. It’s a good point to step back and lay out how all of it fits together. The diagram below is the mental model going forward, and this post walks through every box and the connections between them.
Published:
We just announced RepoDB Connectors, a new home for dedicated, provider-specific ADO.NET data providers built for RepoDB — read the announcement at Introducing RepoDB Connectors — Starting with MariaDB if you haven’t yet. This post goes one level deeper into the first connector that shipped out of it, RepoDb.Connector.MariaDb: why it exists, how it’s laid out internally, the objects it exposes, and enough code to get productive with it right away.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
We are very excited to announce the availability of the PropertyValueAttribute object. It enables you (as a user of the library) to set the property of the IDbDataParameter object before the actual execution against the database.
Published:
Today, we are announcing the availability of RepoDb v1.12.5 and its bundles, the extension libraries at >= v1.1.2. See below.
Published:
When we announced the GA of RepoDB v1.12.0, many users were not able to pre-test the solutions even by having the 4 betas for the last 2 months. This has unfortunately led them to file the issues/bugs right after the releases.
Published:
Today, we are announcing the complete support of RepoDB for the CancellationToken.
Published:
Today, we are announcing the availability of RepoDb v1.12.0. The released packages also come with their bundles, the extension libraries at v1.1.0. See below.
Published:
In this page, we will share with you the differences and what sets RepoDB apart from Dapper. We tried our best to make a 1-to-1 comparison for most areas. This page will hopefully help you decide as a developer to choose RepoDB as your micro-ORM (with a compelling reason).
Published:
We would like to share with you the latest and greatest updates of RepoDB ORM. Recently, we just published the complete out-of-the-box support of Bulk Operations for SQL Server in .NET data access space.
Published:
It was 2 years ago when the first version release of RepoDB was placed at Nuget.org.
Published:
RepoDB has grown from a single hybrid-ORM library into a small family of packages — connectors, bulk operations, and now RepoDB Insights. It’s a good point to step back and lay out how all of it fits together. The diagram below is the mental model going forward, and this post walks through every box and the connections between them.
Published:
RepoDB has grown from a single hybrid-ORM library into a small family of packages — connectors, bulk operations, and now RepoDB Insights. It’s a good point to step back and lay out how all of it fits together. The diagram below is the mental model going forward, and this post walks through every box and the connections between them.
Published:
RepoDB Insights is the companion solution for RepoDB’s Telemetry feature — a six-container stack that receives, stores, and visualizes the operation-level telemetry your application emits. This post walks through standing it up locally: what docker compose up actually does, how to wire an application into it, and what each of the six images is responsible for.
Published:
Even RepoDB is not just another ORM anymore, what started as a Dapper-shaped micro-ORM has grown into a layered platform — see RepoDB’s New Architecture — with its own provider-specific connectors, high-throughput Bulk/Batch operations, and an Insights stack for telemetry sitting above the same core CRUD surface. None of that changes the migration path below — the CRUD layer this post covers is still the part that talks to IDbConnection the same way Dapper does — but it’s worth knowing upfront that migrating gets you a foundation to grow into, not just a like-for-like swap.
Published:
As of writing this, I am busy working on the RepoDB.NET site, providing content to each page.