What is your question 1? What are your concerns? (I see no question marks
there...)
And 2... yes, the LINQ provider is working well, which doesn't mean it's
perfect.
I'm not a NH committer, but I'd recommend it without hesitation.
Diego
On Tue, Jul 13, 2010 at 18:00, Max André Bündchen <[email protected]>wrote:
> That's my first post at nhusers! I found many older post about some of
> my subjects but I can't get a conclusion by myself. The questions is
> general, not detailed, but I hope I can get some tips from the
> experienced users about a direction.
>
> My team is migrating a large project to .Net (large means we have
> about 400 tables in the database splited in 12 integrated modules) and
> we would like to use NHibernate + Linq (that's the reason to use the
> trunk version) to manage data access instead of direct access and T-
> SQL (the current not-.Net version works with T-SQL).
>
> My questions are about:
>
> 1. Performance in cases with huge meta-data/tables (I know, it depends
> a lot of other things).
> 2. There's many post in the group talking about the successful use of
> the new Linq provider in production environments, but is it
> recommended by the developers? The 2k+ unit tests used to verify the
> trunk say yes. :)
>
> Sorry for some mistakes, but English is my third language. :(
>
> --
> 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]<nhusers%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/nhusers?hl=en.
>
>
--
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.
