Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
MariiaI
Devart Team
Posts: 1472
Joined: Mon 13 Feb 2012 08:17

Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Post by MariiaI » Fri 14 Aug 2015 12:38

Thank you for the test project. We will investigate it and contact you as soon as any results are available.

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

Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Post by MariiaI » Tue 18 Aug 2015 08:11

We have reproduced the issue with your test project. We will investigate it in more details and post here about the results.


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

Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Post by MariiaI » Fri 21 Aug 2015 06:18

The bug with the materialization of anonymous types is fixed.
New build of dotConnect for Oracle 8.5.478 is available for download!
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=1&t=32324.

motuzko
Posts: 54
Joined: Tue 08 Sep 2009 18:02
Contact:

Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Post by motuzko » Fri 21 Aug 2015 22:12

Thanks for the update! Will check and report in case I still find some issues.

motuzko
Posts: 54
Joined: Tue 08 Sep 2009 18:02
Contact:

Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Post by motuzko » Thu 27 Aug 2015 15:40

So far, I don't see any issues except maybe a higher CPU utilization.
Thanks for the update!

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

Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Post by MariiaI » Fri 28 Aug 2015 10:21

motuzko wrote:So far, I don't see any issues except maybe a higher CPU utilization.
Thanks for the update!
Could you please provide us with more details regarding the issue with a higher CPU utilization.
Looking forward to your reply.

motuzko
Posts: 54
Joined: Tue 08 Sep 2009 18:02
Contact:

Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Post by motuzko » Wed 30 Sep 2015 17:16

The CPU utilization sample will be the next.

Now I would like you to fix another bug.

Emailing you the test project.


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

Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Post by MariiaI » Thu 01 Oct 2015 09:59

Thank you for the test project, we received it. We will investigate it and contact you by e-mail as soon as possible.


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

Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Post by MariiaI » Wed 07 Oct 2015 05:23

We have reproduced and fixed the issue. We will inform you when the corresponding build of dotConnect for Oracle is available for download.


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

Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types

Post by MariiaI » Fri 16 Oct 2015 05:07

We plan to release new build of dotConnect for Oracle in 1-2 weeks.
We will post here when it is available for download.

Post Reply