Oracle.EntityFrameworkCore US7ASCII Chinese query garbled code

Oracle.EntityFrameworkCore5.21.1,Database encoding format is ‘SIMPLIFIED CHINESE_CHINA.US7ASCII’,The Chinese data queried in .net5 is garbled

services.AddDbContext<FinanceContext>(op => { op.UseOracle(Configuration.GetConnectionString("Finance") , b => b.UseOracleSQLCompatibility("11") ); });

I put the local environment variable 'NLS_ LANG ‘is changed to the same. The query with’ PL / SQL 'is normal, but the Chinese data in. Net5 is garbled

[2881099]

@GaoXiong666 freesql Can you solve the problem of garbled code? Are there any examples for reference? 3Q

To solve this problem, you can try the OLEDB method:

dotnet add package FreeSql.Provider.OracleOledb

public class DB
{
    static Lazy<IFreeSql> oracleLazy = new Lazy<IFreeSql>(() => new FreeSql.FreeSqlBuilder()
        .UseConnectionString(FreeSql.DataType.Oracle, "Provider=OraOLEDB.Oracle;user id=9user;password=123456;data source=//127.0.0.1:1521/XE;Pooling=true;Max Pool Size=2")
        .UseNameConvert(NameConvertType.ToUpper)
        .UseNoneCommandParameter(true)
        .UseMonitorCommand(cmd => Console.WriteLine(cmd.CommandText))
        .Build());
    public static IFreeSql oracle => oracleLazy.Value;
}

var list = DB.oracle.Select<T>().Where(a => a.Id > 100).ToList();

DB.oracle.Insert(new T { ... }).ExecuteAffrows();

DB.oracle.Update<T>()
    .Set(a => a.Name, "china")
    .Set(a => a.Time, DateTime.UtcNow)
    .Where(a => a.Id == 100)
    .ExecuteAffrows();

https://github.com/dotnetcore/FreeSql/wiki

[alexkeh]

There won’t be a fix until there’s a clear resolution on what the course of action should be. This is not a bug. It’s more like an enhancement request. However, the ER would be to emulate other providers’ behavior, which itself is not officially supported.

If you’re looking for an ODP.NET fix, I would recommend opening a service request with Oracle Support. Explain the business case, the technical details and constraints, and the urgency/priority. In that process, we’ll see if there’s any supportable workarounds through some combination of Oracle and customer app changes. If not, there will at least be a better understanding what ODP.NET product changes would have to occur.