Number(1) not mapped to Boolean.

kboeckm · Post by **kboeckm** » Tue 14 Jun 2011 20:59

I'm generated our objects using the 'Update from Database Wizard' found in Entity Developer. I have a database column defined as Number(1). The wizard does not generate a boolean CLR type. Instead, it generates an int32. What could I be doing wrong?

Versions:
Visual Studio 2010
dotConnect: 6.30 professional
LinqConnect: 2.5
Oracle:
server: 10g
client: 11g

StanislavK · Post by **StanislavK** » Wed 15 Jun 2011 17:09

Thank you for the report, we have reproduced this issue. We will inform you when this behaviour is fixed.

As a workaround, you can manually change the Type property of this field to 'System.Boolean'.

kboeckm · Post by **kboeckm** » Wed 03 Aug 2011 16:11

When will this be fixed? Manual workaround is sub optimal since the property type will change everytime the model is generated.

StanislavK · Post by **StanislavK** » Thu 04 Aug 2011 12:11

We are working on this issue. Mapping number(1) to boolean won't be the default behaviour, however, we plan to support the Oracle number mappings in Entity Developer. In this case, you will be able to change the default mappings via the corresponding property of the connection string.

We will post here when this feature is available.

StanislavK · Post by **StanislavK** » Fri 09 Dec 2011 17:01

The possibility of changing the default data type mapping used by Entity Developer is implemented in the latest 3.1.19 build of LinqConnect. The new build can be downloaded from
http://www.devart.com/linqconnect/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only).

For the detailed information about the fixes and improvements available in LinqConnect 3.1.19, please refer to
http://www.devart.com/forums/viewtopic.php?t=22844