NUMBER(1) converted to boolean

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
Post Reply
edstaffin
Posts: 43
Joined: Mon 13 Oct 2008 13:23

NUMBER(1) converted to boolean

Post by edstaffin » Tue 10 Jul 2012 20:36

Is this expected behaviour. I was expecting it to convert to an int32.
Am I missing something? I have to go into the lqml and manually change it.
Thanks ... Ed

MariiaI
Devart Team
Posts: 1472
Joined: Mon 13 Feb 2012 08:17

Re: NUMBER(1) converted to boolean

Post by MariiaI » Wed 11 Jul 2012 11:29

Yes, mapping NUMBER(1) to boolean is the expected behaviour.
However, you can edit a set of predefined type mapping rules since 3.1.19 build of LinqConnect.

Please perform the following steps:
1) Open the 'Options' dialog box in Visual Studio (menu Tools|Entity Developer|Options)
2) Select the Oracle page in the Entity Developer -> Server Options
3) In the 'Type Mapping Rules' grid select the rule you want to edit and сlick 'Edit'
4) In the 'Type Mapping Rule Editor' change the required data in the available boxes and click OK to save your changes.

For more information please refer to http://www.devart.com/dotconnect/oracle ... pping.html and pay attention to corresponding article in the Entity Developer documentation (Common Concepts->Servers' Options->Type Mapping)

Please notify us about the results.

edstaffin
Posts: 43
Joined: Mon 13 Oct 2008 13:23

Re: NUMBER(1) converted to boolean

Post by edstaffin » Wed 11 Jul 2012 13:25

That explains a lot! Thanks for the pointer.
Ed

MariiaI
Devart Team
Posts: 1472
Joined: Mon 13 Feb 2012 08:17

Re: NUMBER(1) converted to boolean

Post by MariiaI » Thu 12 Jul 2012 08:48

If you have any further questions, feel free to contact us.

Post Reply