Invalid SSDL generation [Number(1)]

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Post Reply
JonasJ
Posts: 8
Joined: Wed 25 Nov 2009 08:51

Invalid SSDL generation [Number(1)]

Post by JonasJ » Wed 25 Nov 2009 09:27

When generating a storage model in "entity developer for dotConnect" from Oracle 9, a column of type "NUMBER(1) DEFAULT 3 NOT NULL" gets added as boolean with default value 3.
It is easy to correct this by editing the SSDL but it cannot be correct behavior.

AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Thu 26 Nov 2009 13:37

Do you need Bool with default value true or SByte with default value 3?

JonasJ
Posts: 8
Joined: Wed 25 Nov 2009 08:51

Post by JonasJ » Wed 02 Dec 2009 12:50

AndreyR wrote:Do you need Bool with default value true or SByte with default value 3?
SByte with default value 3

AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Wed 02 Dec 2009 15:59

I will let you know as soon as this issue is adressed.

AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Fri 29 Jan 2010 15:12

Unfortunately, we don't have possibility to map NUMBER(1) DEFAULT 3 NOT NULL to Sbyte.
In the upcoming build the mapping to Int32 with default value 3 will be used.

Post Reply