EF Core 3.1 with nullable enum produces ORA-00904 invalid identifier code

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Eric_08
Posts: 31
Joined: Wed 11 Jul 2018 21:50

Re: EF Core 3.1 with nullable enum produces ORA-00904 invalid identifier code

Post by Eric_08 » Mon 17 Feb 2020 17:15

I'm seeing another issue that's looks like related to 9.11.948 internal build. I'm getting the follow error on the

Code: Select all

OracleConnectionStringBuilder
constructor class. Here is a stack trace with the actual error:

Code: Select all

System.NotSupportedException: Keyword not supported: ''.
   at Devart.Data.Oracle.OracleConnectionStringBuilder.Reset(Keywords index)
   at Devart.Data.Oracle.OracleConnectionStringBuilder.Clear()
   at System.Data.Common.DbConnectionStringBuilder.set_ConnectionString(String value) in /_/src/System.Data.Common/src/System/Data/Common/DbConnectionStringBuilder.cs:line 156
   at Devart.Data.Oracle.OracleConnectionStringBuilder..ctor(String connectionString)
This error started happening only with 9.11.948 internal build. I suspect it's due inclusion of various packages that previous Devart package wasn't including.

kakone
Posts: 12
Joined: Thu 09 Jan 2020 17:30

Re: EF Core 3.1 with nullable enum produces ORA-00904 invalid identifier code

Post by kakone » Tue 18 Feb 2020 10:40

I also encounter this error. We can't use the OracleConnectionStringBuilder with this version. Looking at the code, it seems to be a problem with the OracleConnectionStringBuilder.validKeywords array (an array of length 49 but with only 48 defined items).

Shalex
Site Admin
Posts: 9106
Joined: Thu 14 Aug 2008 12:44

Re: EF Core 3.1 with nullable enum produces ORA-00904 invalid identifier code

Post by Shalex » Tue 18 Feb 2020 14:18

The bug with OracleConnectionStringBuilder is fixed: https://download.devart.com/nuget_oracle_9_11_949.zip.

Eric_08
Posts: 31
Joined: Wed 11 Jul 2018 21:50

Re: EF Core 3.1 with nullable enum produces ORA-00904 invalid identifier code

Post by Eric_08 » Tue 18 Feb 2020 20:53

The new version fixed OracleConnectionStringBuilder issue. The only remaining issue that's left is inclusion of Microsoft.Windows.Compatibility v2.0.1 package in Devart.Data.Oracle package, which adds various DLLs that previous Devart.Data.Oracle wasn't doing before.

Eric_08
Posts: 31
Joined: Wed 11 Jul 2018 21:50

Re: EF Core 3.1 with nullable enum produces ORA-00904 invalid identifier code

Post by Eric_08 » Thu 20 Feb 2020 14:08

Devart team,
I need an official build with no dependency on Microsoft.Windows.Compatbility package. When can you publish the official version? I need to upgrade my application to .NET Core 3.1/EF Core 3.1. It's really urgent that official update is provided within next week.

Shalex
Site Admin
Posts: 9106
Joined: Thu 14 Aug 2008 12:44

Re: EF Core 3.1 with nullable enum produces ORA-00904 invalid identifier code

Post by Shalex » Tue 25 Feb 2020 14:57

There is no timeframe for the new public build at the moment. We will provide the internal build with no dependency on Microsoft.Windows.Compatbility package and include the fix in the next public build.

Shalex
Site Admin
Posts: 9106
Joined: Thu 14 Aug 2008 12:44

Re: EF Core 3.1 with nullable enum produces ORA-00904 invalid identifier code

Post by Shalex » Thu 27 Feb 2020 12:00

The internal build with the fix is available at http://download.devart.com/nuget_oracle_9_11_956.zip.

Eric_08
Posts: 31
Joined: Wed 11 Jul 2018 21:50

Re: EF Core 3.1 with nullable enum produces ORA-00904 invalid identifier code

Post by Eric_08 » Thu 27 Feb 2020 16:41

Just got the latest internal build. Footprint looks much smaller, which is great. Everything also appears to be working. Will be looking for official build, but so far, so good.

Post Reply