Running Oracle .350 with EF 4.3.1: initializing the database

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Post Reply
robcube
Posts: 7
Joined: Thu 19 Apr 2012 11:00

Running Oracle .350 with EF 4.3.1: initializing the database

Post by robcube » Tue 01 May 2012 15:48

Bug?

EntityFramework.dll 4.3.1
Devart.Data 5.0.449.0
Devart.Data.Oracle, Devart.Data.Oracle.Entity, Devart.Data.Oracle.Entity.Migrations 6.80.350.0

Works fine using EntityFramework 4.2.


---------------------------
Error: An exception occurred while initializing the database. See the InnerException for details. Schema specified is not valid. Errors:
(7,6) : error 0040: The Type nvarchar2 is not qualified with a namespace or alias. Only primitive types can be used without qualification.
(8,6) : error 0040: The Type timestamp is not qualified with a namespace or alias. Only primitive types can be used without qualification.
(9,6) : error 0040: The Type blob is not qualified with a namespace or alias. Only primitive types can be used without qualification.
(10,6) : error 0040: The Type nvarchar2 is not qualified with a namespace or alias. Only primitive types can be used without qualification. at System.Data.Entity.Internal.InternalContext.PerformInitializationAction(Action action)
at System.Data.Entity.Internal.InternalContext.PerformDatabaseInitialization()
at System.Data.Entity.Database.Initialize(Boolean force)

Shalex
Devart Team
Posts: 8033
Joined: Thu 14 Aug 2008 12:44

Re: Running Oracle .350 with EF 4.3.1: initializing the data

Post by Shalex » Wed 09 May 2012 09:20

The EntityFramework.dll versions 4.1/4.2 (Code-First) and 4.3.x/5.x (Code-First Migrations) have different implementations. When you are using 4.3.x/5.x, it is necessary to turn on the ColumnTypeCasingConventionCompatibility configuration option: http://blogs.devart.com/dotconnect/inde ... Convention .

Post Reply