RepoDB is an open-source .NET ORM library that bridges the gaps of micro-ORMs and full-ORMs. It helps you simplify the switch-over of when to use the BASIC and ADVANCE operations during the development.

It is your best alternative ORM to both Dapper and EntityFramework.

👋 Hey Scott, thank you for endorsing RepoDB into the community of .NET.

We are announcing the GA of RepoDB v1.12.4 and its extended packages at v1.1.1. This release has included the complete support to the CancellationToken.

Please also be reminded of the recent GA of RepoDB v1.12.0, one of the biggest release of this library. In this release, we covered the support to F#, Class Handler, Advanced and New Enhanced Compiler, Typed Results and many more.

Read more from our official blog release notes and/or in the official Github release page.

Like with any other ORMs, RepoDB does provide the preliminary methods needed for your basic operations (i.e.: CRUD). The good thing is, RepoDB also does provide the operations that is needed to cater your edge-cases like 2nd-Layer Cache, Tracing, Repositories, Property Handlers and Batch/Bulk Operations.

If you are to use RepoDB, your development experience is as simple as Dapper when opening a connection and is as simple as Entity Framework when executing an operation. It is the reason that makes this library the simpliest ORM to use.

When you do the bulk operations, the generated value of the identity columns will be set back to the data models, just right after your execution. It is an important use-case that is/may needed by you and/or most developers, and both the BulkInsert and BulkMerge operations addressed this need.

RepoDB also does support the different way-of-executions (the atomic, the batch and the bulk). Through this, it is easy for you to establish your repository that can process the smallest-to-the-largest datasets without even affecting the efficiency and the performance of your application.

Please click any of the link below to fast-track your learnings.

• SqlServer
• SqLite
• MySql
• PostgreSql

Or, learn a specific feature.

• Batch Operations
• Bulk Operations
• Caching
• Class Handlers
• Class Mapping
• Dynamics
• Connection Persistency
• Enumeration
• Expression Trees
• Hints
• Implicit Mapping
• Multiple Query
• Property Handlers
• Repositories
• Targeted Operations
• Tracing
• Transaction
• Type Mapping

Otherwise, please visit our documentation page to learn more.

The execute methods below support all the RDBMS data providers.

• ExecuteQuery
• ExecuteNonQuery
• ExecuteScalar
• ExecuteReader
• ExecuteQueryMultiple

Whereas the fluent methods below only support the SQL Server, SQLite, MySQL and PostgreSQL RDBMS data providers.

• Query
• Insert
• Merge
• Delete
• Update

Click here to see all the operations.

By default, .NET is auto-resolving the references, however, we strongly recommend that you always explicitly reference the RepoDb core library. The rationale behind this is that, the RepoDb core library is a fast-moving package in which all the alpha/beta releases, hotfixes and/or even the actual releases could happen without affecting the extension libraries.

Please note that we are releasing an actual next released-version if the changes are having minimal impact but is important for the other users.

You can always target the version when installing the library, even it is on a semantic release.

> Install-Package RepoDb -version 1.x.x-betaX

By default, RepoDB does not do the automatic .NET CLR Type conversion during the serialization and deserialization process. The coercion support is completely dependent to the ADO.NET coercion capability.

It is in purpose to strictly notify you (as a library user) the design and/or the implementation problem of the Model if being compared to its corresponding database Table.

If you wish to have an automatic conversion, simply set the Converter.ConversionType property to Automatic.

RepoDb.Converter.ConversionType = ConversionType.Automatic;

Note: The exception that is being thrown is dependent to what the underlying ADO.NET coercion exception. If the Automatic conversion is used, the extracted value will always be evaluated and an additional conversion logic will be used (if needed). The conversion logic is through the AOT compilation of System.Linq.Expressions.Expression.Convert and/or System.Convert.

It is very important for you and to the community of .NET to learn the things the library is capable and is-not capable of doing, so please spend time reading the limitation page before using the library.

The benchmark result shown on this section is the result of the community-approved ORM bencher tool, the RawDataAccessBencher tool.

Below is the actual recent official execution result.

We would like to make RepoDB the mainstream hybrid-ORM library for .NET technology. Please help us build and realize the solution.

To contribute, please find a for-grabs item and issue a PR. Otherwise, you may create a new issue for us to look-at and discuss.

If you wish to contribute to the documentation site, it is hosted in the RepoDb.NET repository. Your expertise is needed to correct the forms, if needed.

Your biggest contribution is to utilize and share this library to the other developers.

• Blog it
• Discuss it
• Document it
• Share it
• Use it

Or, show your support by simply giving a ⭐ on this project.

Please get in touch with us via:

• GitHub - for any issues, requests and problems.
• StackOverflow - for any technical questions.
• Twitter - for the latest news.
• Gitter Chat - for direct and live Q&A.

• Building the Solutions - let us build your copies.
• Coding Standards - let us be uniformed.
• Issuing a Pull-Request - let us be aligned and notified.
• Reporting an Issue - let us be organized for easy tracking and fixing.

Thanks to all the contributors of this project, and to Scott Hanselman for Exploring the .NET open source hybrid ORM library RepoDB.

And also, thanks to these awesome OSS projects.

• AppVeyor - for the builds and test-executions.
• GitHub - for hosting this project.
• Gitter - for the community engagements.
• Jekyll - for powering our website.
• Moq - for being the tests mocking framework.
• Nuget - for the package deliveries.
• RawDataAccessBencher - for measuring the performance and efficiency.
• ReadTheDocs - for the library documentations.
• SharpLab - for helping us on our IL coding.
• Shields - for the awesome badges.
• StackEdit - for being the markdown file editor.
• Microsoft.Data.Sqlite, System.Data.SQLite.Core, MySql.Data, MySqlConnector, Npgsql - for being the extended DB provider drivers.

Apache-2.0 - Copyright © 2019 - Michael Camara Pendon