Column Mapping - LinqConnect

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Post Reply
meetkarthik
Posts: 9
Joined: Thu 16 Sep 2010 20:10

Column Mapping - LinqConnect

Post by meetkarthik » Tue 21 Sep 2010 19:16

When i add a table with the following definition

CREATE TABLE "TEST"
( "ID" NUMBER(19) NOT NULL ENABLE,
CONSTRAINT "TEST_PK" PRIMARY KEY ("ID")
)

in the model , the column ID is automatically mapped as 'Decimal' instead of 'Int64'

This seems to be working fine in Entity framework. The problem is happening only with LinqConnect.

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Wed 22 Sep 2010 11:29

LinqConnect uses the type returned by OracleDataReader. For Number(19) this is Decimal; we do not plan to change this behaviour, as this can affect compatibility with prior dotConnect for Oracle versions.

We are working on the possibility of configuring Oracle number mappings in the connection string, but cannot provide any timeframe for this. At the moment, a possible workaround is to set the needed type manually.

meetkarthik
Posts: 9
Joined: Thu 16 Sep 2010 20:10

Post by meetkarthik » Wed 22 Sep 2010 20:40

Thanks for clarifying..

Post Reply