Search found 2 matches

by DavidC
Thu 14 Jul 2011 13:22
Forum: Entity Framework support
Topic: EF Code First - The Type clob is not qualified with a namesp
Replies: 2
Views: 5829

Worked a treat, thanks for the fast and comprehensive response. :D
by DavidC
Thu 14 Jul 2011 10:17
Forum: Entity Framework support
Topic: EF Code First - The Type clob is not qualified with a namesp
Replies: 2
Views: 5829

EF Code First - The Type clob is not qualified with a namesp

Using Entity Framework Code First to connect to Legacy Oracle Database with devart dotconnect.

I keep getting this error:
The Type clob is not qualified with a namespace or alias. Only PrimitiveTypes can be used without qualification.

I have been trying out to use EF 4.1 (code first) with MVC 3, against a legacy Oracle 10g database, using devart dotconnect. The legacy database **cannot** be changed. I'm trying to read the data in it out to a webpage.

(Devart.Data.Oracle Version: 5.70.140.0)

I've had a few errors to overcome along the way, but came to this one.

This is my code:

Web.config connection info:

Code: Select all

   

Code: Select all

    namespace AllInOne
    {
    	public class OdeToTrainingCoursesDB : DbContext
    	{
    		public DbSet VENUES { get; set; }
    	}
    }

Code: Select all

    using System.ComponentModel.DataAnnotations;
    
    namespace AllInOne.Models
    {
    	public class VENUES
    	{
    		[Key]
    		public int VENUE_ID { get; set; }
    	}
    }
This is the first table (of many) that I'm trying to read from.

Code: Select all

    CREATE TABLE VENUES
    (
      VENUE_ID    NUMBER(10)                        NOT NULL,
      VENUE_TYP   VARCHAR2(1 BYTE),
      BASE_ORG    NUMBER(10)                        NOT NULL,
      COUNTY      VARCHAR2(35 BYTE)
    )