search

nreco / data

Fast DB-independent DAL for .NET Core: abstract queries, SQL commands builder, schema-less data access, POCO mapping (micro-ORM).
https://www.nrecosite.com/dalc_net.aspx
MIT License
183 stars 39 forks source link

Missing type in NReco.Data Latest Stable 1.1.1 #59

Closed xavidram closed 4 years ago

xavidram commented 4 years ago

Upon working on a new project, I added the latest NReco.Data stable packages along with the latest NReco.GraphQL package. When executing a GraphQL query, the exception response is as follows:

image

I am able to fix this issue by downgrading the NReco.Data package to version 1.0.6 which seems to have the NReco.Data.ListSortDirection assembly in the package. The Version 1.1.1 does not seem to have it included.

My project is working fine with NReco.Data version 1.0.6, but I just wanted to mention the missing assembly in the latest stable version.

VitaliyMF commented 4 years ago

@xavidram there was a breaking change in 1.1.0 related to ListSortDirection (see notes here https://www.nuget.org/packages/NReco.Data/).

In short, there was own enum NReco.Data.ListSortDirection because in early .NET Core 1.x days type System.ComponentModel.ListSortDirection was missed. However, in netstandard20 it is available, and .NET Core 1.x is not used any more. So in version 1.1.0 own enum was removed to avoid any possible ambiguity.

All this means that you cannot upgrade NReco.Data to 1.1.0 if you use existing release of NReco.Graphql because of this breaking change. In upcoming release of NReco.Graphql reference to NReco.Data will be upgraded to 1.1.1.

xavidram commented 4 years ago

That makes sense. I should have read the changelog. If it is not too much of an bother. Could you give me an insight as to how the NrecoGraphQL is querying Relex subqueries?

I have two Tables as follows:

Employee (ID int, DivisionID int, ....) Division(ID int, Name varchar(50), ...)

the Schema object for employees is as follows: image

And Division Schema object is as follows: image

The Relex string's on the Employee Schema seem correct from what I have seen in the documentation. But oddly enough, for any query that calls a Relex query, it always returns the last item in the table

image

Is there a fallback that the Relex query executor could fall back to that would cause it to grab the last item in the table?

MakaBuka commented 4 years ago

@xavidram It's related to commercial component NReco.GraphQL, so, check you email box - I've sent workaround.