Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
Thank you for the test project. We will investigate it and contact you as soon as any results are available.
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
We have reproduced the issue with your test project. We will investigate it in more details and post here about the results.
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
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.
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.
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
Thanks for the update! Will check and report in case I still find some issues.
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
So far, I don't see any issues except maybe a higher CPU utilization.
Thanks for the update!
Thanks for the update!
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
Could you please provide us with more details regarding the issue with a higher CPU utilization.motuzko wrote:So far, I don't see any issues except maybe a higher CPU utilization.
Thanks for the update!
Looking forward to your reply.
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
The CPU utilization sample will be the next.
Now I would like you to fix another bug.
Emailing you the test project.
Now I would like you to fix another bug.
Emailing you the test project.
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
Just in case you did not get the e-mail:
Project http://motuzko.com/obsilf/Downloads/Dot ... Bug003.rar
DDL.sql - is in the archive
Project http://motuzko.com/obsilf/Downloads/Dot ... Bug003.rar
DDL.sql - is in the archive
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
Thank you for the test project, we received it. We will investigate it and contact you by e-mail as soon as possible.
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
We have reproduced and fixed the issue. We will inform you when the corresponding build of dotConnect for Oracle is available for download.
Re: Looks like the LinqConnect library gets confused when materializing objects with the same name nested in different types
We plan to release new build of dotConnect for Oracle in 1-2 weeks.
We will post here when it is available for download.
We will post here when it is available for download.