RepoDb.Oracle 0.0.1-alpha1

RepoDb.Oracle — RepoDB for Oracle Database

The Oracle provider for RepoDB — a fast, lightweight .NET ORM that lets you use raw SQL and fluent operations side by side on the same connection. Built on top of RepoDb and ODP.NET (Oracle.ManagedDataAccess.Core).

Target

Oracle Database 12c and later. Earlier versions are not supported (the provider relies on native IDENTITY columns, OFFSET/FETCH paging, and implicit result sets, all of which require 12c+).

Important Pages

• GitHub Home — core library and source code.
• Website — full documentation, API reference, and blog.

Community

• GitHub Issues — bug reports and feature requests.
• StackOverflow — technical questions.
• Microsoft Teams — live Q&A.
• X / Twitter — news and updates.

Dependencies

• Oracle.ManagedDataAccess.Core — ODP.NET Oracle data provider.
• RepoDb — the RepoDB core library.

License

Apache-2.0 — Copyright © 2026 Michael Camara Pendon

Installation

Install-Package RepoDb.Oracle

Or visit the installation page for more options.

Get Started

Initialize the bootstrapper once at application startup:

GlobalConfiguration
    .Setup()
    .UseOracle();

Then use any RepoDB operation directly on your OracleConnection:

Query

using (var connection = new OracleConnection(ConnectionString))
{
	var customer = connection.Query<Customer>(c => c.Id == 10045);
}

Insert

var customer = new Customer
{
	FirstName = "John",
	LastName = "Doe",
	IsActive = true
};
using (var connection = new OracleConnection(ConnectionString))
{
	var id = connection.Insert<Customer>(customer);
}

Update

using (var connection = new OracleConnection(ConnectionString))
{
	var customer = connection.Query<Customer>(10045);
	customer.FirstName = "John";
	customer.LastUpdatedUtc = DateTime.UtcNow;
	var affectedRows = connection.Update<Customer>(customer);
}

Delete

using (var connection = new OracleConnection(ConnectionString))
{
	var customer = connection.Query<Customer>(10045);
	var deletedCount = connection.Delete<Customer>(customer);
}

QueryMultiple Behavior

QueryMultiple/QueryMultipleAsync return several result sets — one per target type — from a single call.

ODP.NET rejects a command text containing more than one SQL statement (IDbSetting.IsMultiStatementExecutable = false for RepoDb.Oracle), so QueryMultiple automatically falls back to issuing one round trip per requested type instead of one combined command. This fallback is transparent — the same QueryMultiple<T1, T2, ...> call works unchanged against Oracle — but it means a call that costs 1 round trip on SQL Server/MySQL/PostgreSQL costs N round trips (one per type) on Oracle. Keep this in mind for latency-sensitive code paths that call QueryMultiple with many types against an Oracle database.

Known limitations (v1)

InsertAll / MergeAll

Execute one row per round-trip for now (IsMultiStatementExecutable = false); true multi-row batching with a single implicit-result-set return will follow in a later release.

Identity/primary-key

Retrieval on Insert/Merge relies on an Oracle 12c+ implicit result set (DBMS_SQL.RETURN_RESULT) wrapped in an anonymous PL/SQL block, since Oracle's native RETURNING ... INTO binds to an output parameter that RepoDb's core execution pipeline does not read back.

DECLARE l_repodb_result "CompleteTable"."Id"%TYPE; l_repodb_cursor SYS_REFCURSOR; BEGIN INSERT INTO "CompleteTable" ( "SessionId", "ColumnVarchar", "ColumnNumber", "ColumnDate", "ColumnTimestamp" ) VALUES ( :SessionId, :ColumnVarchar, :ColumnNumber, :ColumnDate, :ColumnTimestamp ) RETURNING "Id" INTO l_repodb_result; OPEN l_repodb_cursor FOR SELECT l_repodb_result AS "Result" FROM DUAL; DBMS_SQL.RETURN_RESULT(l_repodb_cursor); END;

This should be verified against your own Oracle instance before relying on it in production.

RETURNING on MERGE

A RETURNING clause on MERGE specifically is only supported starting with Oracle Database 23ai - it does not work on 12c/18c/19c/21c at all (fails with ORA-00933). This provider otherwise targets 12c+, but Merge against a table with a primary/identity key requires 23ai+ to get the key value back. On older versions, Insert/Update/Query/etc. are unaffected - only identity-returning Merge calls are impacted.

GUID/UNIQUEIDENTIFIER

Oracle has no native GUID/UNIQUEIDENTIFIER type. A System.Guid data entity property will throw ArgumentException: Value does not fall within the expected range. from OracleParameter.Value if bound directly, because (unlike SqlParameter/NpgsqlParameter) ODP.NET does not accept a raw Guid value. If a column stores a GUID as RAW(16), map it as byte[] on the entity, or keep it as Guid and register RepoDb.Oracle.PropertyHandlers.GuidToByteArrayPropertyHandler for that specific property:

PropertyHandlerMapper.Add<YourEntity, GuidToByteArrayPropertyHandler>(
    e => e.YourGuidProperty, new GuidToByteArrayPropertyHandler(), true);

Register it per-property (not globally for typeof(Guid)) if your process also uses another RepoDb provider that handles Guid natively, since a type-level PropertyHandlerMapper registration applies process-wide across all connections.