Navigation Properties

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
Post Reply
LPCRoy
Posts: 7
Joined: Mon 18 May 2009 20:45

Navigation Properties

Post by LPCRoy » Tue 19 May 2009 23:19

Hi,
I'm having a problem with using Navigation properties. If I try to include a navigation property in the select list of my query, I get the error "Specified method is not supported."
With the following stack trace

at Devart.Data.Linq.Provider.Query.bf.a.a(bh A_0)
at Devart.Data.Linq.Provider.Query.SqlVisitor.a(SqlNode A_0)
at Devart.Data.Linq.Provider.Query.SqlVisitor.c(SqlExpression A_0)
at Devart.Data.Linq.Provider.Query.SqlVisitor.a(bo A_0)
at Devart.Data.Linq.Provider.Query.SqlVisitor.a(ax A_0)
at Devart.Data.Linq.Provider.Query.bf.a.a(ax A_0)
at Devart.Data.Linq.Provider.Query.SqlVisitor.a(SqlNode A_0)
at Devart.Data.Linq.Provider.Query.bf.a(SqlNode A_0, SqlNode A_1, SqlFactory A_2, ao A_3)
at Devart.Data.Linq.Provider.DataProvider.a(b A_0, Type A_1, SqlNode A_2, IList`1 A_3)
at Devart.Data.Linq.Provider.DataProvider.a(Expression A_0)
at Devart.Data.Linq.Provider.DataProvider.h(Expression A_0)
at Devart.Data.Linq.DataQuery`1.i()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at LokiUI.MainWindow..ctor() in C:\Users\rowillia\XTest\XTest\LokiUI\Main.xaml.cs:line 36

For example, the following code sample will throw an exception

Code: Select all

from x in dataContext.Table
select x.y
What's odd is that if I select properties on the child I've navigated to, everything works fine. The following code sample executes with no problems:

Code: Select all

from x in dataContext.Table
select x.y.Propery
Any ideas?

Thanks,
Roy

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

Post by AndreyR » Wed 20 May 2009 09:12

Thank you for the report, we have reproduced the problem.
I will let you know about the results of our investigation.

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

Post by AndreyR » Tue 16 Jun 2009 14:34

This problem is fixed in the upcoming build of dotConnect for PostgreSQL.

Post Reply