Coject.Core.Database 1.0.5

Coject.Core.Database

Coject.Core.Database is the provider-neutral .NET 8 / .NET 10 runtime contract and compatibility facade used by Workshop-generated DAL code.

The base package contains no Oracle, PostgreSQL, SQL Server, MariaDB, Access, OleDb, or Dapper implementation. Install one separately versioned provider package, such as Coject.Core.Database.Oracle, beside the base package.

Compatibility facade

Existing generated consumers continue to use the CojectCore.Database namespace and InitializeDB members, including the historical spellings Paramters, ClearAllParmters, and SaveDataRetDatatTable.

var configuration = new ConfigurationSetting
{
    Provider = "Oracle",
    DataBaseType = ClientDataBase.ORACLE, // numeric transition fallback
    ConnectionString = connectionString
};

var database = new InitializeDB(configuration);
database.Paramters.InputParam.Add(new InitializeDB.InputParameter(
    "PUSER_ID",
    userId,
    22,
    InitializeDB.ParamTypes.NUMBER));

var succeeded = database.ExecuteNonQuery("SECURITY_224.PRC_USER_SAVE");

Provider is authoritative when supplied. If the legacy numeric DataBaseType is also supplied, both values must agree. A missing provider package produces the stable DB-PROVIDER-NOT-INSTALLED outcome.

Provider contract

A provider package exposes a public parameterless IDatabaseProviderFactory. The factory is stateless, declares a DatabaseProviderManifest, and creates an IDatabaseProvider from DatabaseProviderOptions. Providers implement genuine synchronous and asynchronous execution; synchronous execution must not block an asynchronous implementation.

Resolution rejects manifests whose provider/assembly identity is not canonical, whose contract is not compatible with runtime contract 1.0, or which omit the required sync, async, stored-procedure, transaction, named-result, or scalar-output capabilities.

Each provider execution owns its connection, command, reader, and transaction until all ordered result tables and scalar outputs are materialized. It commits only after complete successful materialization and rolls back provider or business failures.

Runtime guarantees

• Mutable facade parameters are snapshotted before execution.
• Legacy bulk string[] parameters remain typed arrays and are defensively cloned.
• One provider is selected per facade/application instance.
• Overlapping calls on the same facade instance are rejected.
• No command is automatically retried.
• Cancellation is propagated by asynchronous APIs.
• Telemetry contains provider, routine, correlation, duration, and outcome only.
• Parameter values, returned rows, connection strings, and secrets are never sent to the execution observer.

Compatibility boundary

The historical public low-level oraConnCls and pgConnCls types exposed vendor driver types and therefore cannot remain in the vendor-free base assembly. Their source files remain in this checkout as baseline evidence but are excluded from compilation. Repository evidence found no generated or shared consumer that directly calls them. Applications that did use those unsupported low-level types must migrate to the neutral provider contract or a provider package API.

Package publication and production rollout require separate authorization.