To be frankly ?

On Fri, Aug 6, 2010 at 2:06 PM, Kevin Anderson
<[email protected]>wrote:

>  Fabio,
>
> I guess that was what I was originally looking for in the documentation. I
> was totally aware of the fact that by moving to NH3 and using the 'embedded
> linq-provider' that likely there would be upgrade issues. What I was looking
> for was:
>
> 1. Is it expected that NH3 users would be expected to switch to the
> embedded provider or have the option of using either.  In other words, will
> nhibernate.linq be dropped?
>

I don't know. The code is there and it is a separated DLL and you can use
the new embedded provider with the Contrib-provider all together.


>
> 2. To move from nhibernate.linq 1.0 to nh3 embedded linq provider, what
> would be the required code changes. For example, change references, change
> linq to Query, and then what?
>

Fetch instead of Expand and some other things.

Are they entirely different, is the new embedded linq-provider meant to be a
> replacement, or something in between?
>

They are completely different internally and externally.


> 3. Is there any documentation on using the embedded linq-provider or should
> I just be expecting it to work like any other linq provider?
>

You have to expect that it work like NH3-linq-provider... we can't recreate
the same bugs and issues are present in others providers; we have our own

>
> Thanks,
> Kevin
>

To be frankly ? (again)
You can create a failing test and open a new JIRA ticket, then we can check
which is the problem. (<== time 3)

-- 
Fabio Maulo

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en.

Reply via email to