There is an open issue on Jira for 
this: https://nhibernate.jira.com/browse/NH-3556.

RP

On Friday, September 18, 2015 at 3:06:49 PM UTC+1, Don Lavelle wrote:
>
> Hi, all,
>
> I've started using the Microsoft.AspNet.OData library to serve OData as a 
> RESTful web API. I've been using the NHibernate LINQ provider for several 
> years now to access the database backend, and I'd like to continue doing 
> so. I'm not sure how I can get OData to work with NHibernate in my 
> situation. For simple data, it works just find, but I find whenever I have 
> to use the *$expand* parameter, I get a variety of exceptions. I've 
> abstracted the data access layer and am fairly effectively using NHibernate 
> automapping with custom conventions, so our developers rarely have to think 
> about NHibernate. The two typical ways to retrieve data by either getting 
> an IQueryable from the data access object or by passing in a LINQ 
> expression that is used to select the desired data. The NH doesn't seem to 
> support the IQueryable operations AspNet.Odata is doing.
>
> One problem, I posted about earlier to no avail. (Sorry again for the 
> double-post. I thought after my first post was moderated, the second would 
> go through immediately.) Another problem I'm facing seems to be the problem 
> described in this SO question: 
> http://stackoverflow.com/questions/20582806/error-using-expand-with-nhibernate-and-webapi-odata
> .
>
> Is this something that the NH community is not interested in, or has no 
> one stepped up to do the work to make it happen? I'd certainly be 
> interested in seeing it work and could contribute a little bit, but I don't 
> have the NH expertise or time to do it on my own.
>
> Thanks,
>
>     Don
>

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.

Reply via email to