OceanBase Connector/NET V1.3.0

Version information

• Release date: August 11, 2026
• Version: V1.3.0 (OceanBase.ManagedDataAccess.1.3.0)
• ORM framework adaptation packages:
  • OceanBase.EntityFrameworkCore8.1.1.0.nupkg
  • SqlSugarCore.OceanBase.1.1.0.nupkg
  • FreeSql.Provider.OceanBase.1.1.0.nupkg

Overview

OceanBase Connector/NET V1.3.0 focuses on enhancing compatibility with Oracle data types,.NET ecosystem versions, and character sets. It introduces support for User-Defined Types (UDTs), enabling INSERT, UPDATE, and SELECT operations on complex types such as OBJECT and VARRAY, while being compatible with the native Oracle driver interface. It also adds support for the GBK character set, allowing users to specify the character set via the CharSet configuration parameter. Furthermore, it supports Full Compatibility mode of FreeSql Framework for all .NET versions. Additionally, V1.3.0 fixes several critical issues, including abnormal AutoEnlist parameters, ArrayBinding errors, and null pointer exceptions in DeriveParameters, further improving the stability and compatibility of the driver.

We recommend that you use this version to verify migration, conduct compatibility testing, and adapt your business for migrating .NET applications from Oracle to OceanBase.

Key features

Support for UDTs (User-Defined Types)

OceanBase Connector/NET V1.3.0 introduces support for User-Defined Types (UDTs). It supports INSERT/UPDATE/SELECT operations for OBJECT and VARRAY types, covering both binary and text protocols. It supports nested UDTs (Object nested within Object, Object nested within VARRAY, VARRAY nested within Object, and multi-level nesting) and supports automatic derivation of UDT parameter types for stored procedures using DeriveParameters. Meanwhile, it is compatible with the native Oracle driver interface, supporting standard interfaces such as IOracleCustomType, OracleUdt.SetValue, and GetValue. This feature significantly reduces the workload required to migrate Oracle applications to OceanBase, enhancing Oracle compatibility and migration efficiency.

For more information, see UDTs (User-Defined Types).

Support for GBK Character Set

OceanBase Connector/NET V1.3.0 adds support for the GBK character set. Users can specify the character set in the connection string via the CharSet parameter, and the driver uses GBK encoding for encoding and decoding based on the configuration. It supports reading and writing Chinese characters of types such as VARCHAR2, CHAR, and CLOB under the GBK character set, and supports cross-encoding access between GBK tenants and UTF-8 tenants. Meanwhile, the NCHAR and NVARCHAR2 types still use NCharacterEncoding (UTF-8) for encoding and decoding, unaffected by the CharacterSet parameter, ensuring that Unicode characters outside the GBK range (such as "㐀" U+3400) can still be correctly stored and accessed. This feature significantly reduces migration and adaptation costs in GBK character set scenarios, enhancing Oracle compatibility.

Note: When using the GBK character set, the corresponding ORM frameworks (FreeSql, SqlSugar, EF Core 8) need to be updated accordingly.

For more information about connection string parameters, see Connection string.

Full Compatibility mode of FreeSql Framework for all .NET versions

The FreeSql.Provider.OceanBase adaptation package released with OceanBase Connector/NET V1.1.0 only supports .NET 6.0 and .NET 8.0. To cover more .NET versions, the new version of the FreeSql adaptation package adds compatibility with all .NET versions, including .NET 7.0.

For more information, see Use FreeSql.

Compatibility changes

Parameter changes

Supported OBServer versions

It supports OBServer 4.x, OBServer 3.x, and earlier versions.

We recommend that you use the OBServer 4.x series for optimal compatibility and performance.

Key fixes

• Fixed the issue where AutoEnlist + TransactionScope release exception occurred.
• Fixed the issue where data misalignment occurred due to inconsistent multi-OUT column counts with client declarations.
• Added support for reading REF CURSOR result sets using ExecuteReader andDataAdapter.Fill.
• Fixed ArrayBinding parameter binding errors and type conversion validation issues.
• Fixed the issue where the NCLOB type was not supported when generated by the FreeSql framework.
• Fixed the issue where service registration was incomplete during EF Core design.
• Added support for reading LOB types using the Dapper framework.
• Added support for ORM adaptation of NCHAR / NVARCHAR.
• Fixed the issue where obtaining UDT and REF CURSOR parameter information via DeriveParameters was abnormal.