Awesome! As you all now / have guessed, I've been completely snowed
under with work-related work for the last couple of months, and have had 100%
intention but 0% time to do anything with the Linq provider. And it's really
pained me to have done so much work, to know that it'
Weborb is a real-world demostration on how use NH, especially HQL, in
a RIA... even direcly from jscript or whatvever you want.
But... well... In .NET world LINQ is the real COOL thing.
--
Fabio Maulo
El 29/11/2010, a las 11:32, Kakone escribió:
> On 26 nov, 03:17, Dmitry wrote:
>> I want to
On 26 nov, 03:17, Dmitry wrote:
> I want to say thanks to Patrick for trying improve the LINQ provider.
> In my opinion, and it seems like I am not alone, LINQ is the biggest
> usable addition to the NH3.
You are not alone :-)
As I'm trying to use NHibernate with WCF RIA Services, LINQ is very
im
Totally agree. Thanks Patrick.
On Nov 26, 3:17 am, Dmitry wrote:
> I want to say thanks to Patrick for trying improve the LINQ provider.
> In my opinion, and it seems like I am not alone, LINQ is the biggest
> usable addition to the NH3.
>
> Everyone should realize that even though LINQ is by far
I want to say thanks to Patrick for trying improve the LINQ provider.
In my opinion, and it seems like I am not alone, LINQ is the biggest
usable addition to the NH3.
Everyone should realize that even though LINQ is by far not the only
way to create queries in NHibernate, it makes NHibnerate much
> *From:* nhibernate-development@googlegroups.com [mailto:
> nhibernate-developm...@googlegroups.com] *On Behalf Of *Fabio Maulo
> *Sent:* Wednesday, November 24, 2010 1:32 PM
>
> *To:* nhibernate-development@googlegroups.com
> *Subject:* Re: [nhibernate-development] Re: NHibernate 3 and Li
Wednesday, November 24, 2010 1:32 PM
To: nhibernate-development@googlegroups.com
Subject: Re: [nhibernate-development] Re: NHibernate 3 and Linq Provider
don't worry, the frustration is mutual.
On Wed, Nov 24, 2010 at 8:29 AM, Stefan Wenig
mailto:stefan.we...@rubicon.eu>> wrote:
On
don't worry, the frustration is mutual.
On Wed, Nov 24, 2010 at 8:29 AM, Stefan Wenig wrote:
> On 23 Nov., 17:09, Fabio Maulo wrote:
> > I like LINQ (to object)
>
> That about sums up the problems I have communicating with you, and the
> frustration I'm experiencing.
--
Fabio Maulo
Patrick,
congratulations, glad you're in! I'm not a member of NH, but I'm in
charge of re-linq, which NH's LINQ provider builds upon. re-linq
basically just works, but there have been a few issues in the past
that we could solve for you (like VB support), that we will solve soon
(like using IQuery
On 23 Nov., 17:09, Fabio Maulo wrote:
> I like LINQ (to object)
That about sums up the problems I have communicating with you, and the
frustration I'm experiencing.
My commitment is to contribute what time and ideas I have to improving
NHibernate. I want to help, not just in code, but in areas such as
documentation, testing, and packaging. For the time being, I intend to
focus my energy on solidifying the Linq provider, fixing issues and
providing even more
A note about people scared by NH codebase.
Don't worry!! I know many areas of NH codebase but nobody can say "I know
all NHibernate".
NHibernate changes day by day and it has (only in nhibernate\src\NHibernate)
3500 files in 829 folders.
Nobody of NHibernate committers have received a "guide line d
James,
have you heard me saying that the LINQ-provider is the most important
feature of NH3 and it represent the better way to query the DB in NH3 ?
Did you read a post announcing the final release of NH3 ?
Can you, and some others NH's MVP, write some posts with yours opinions
about the coming so
t;
> Stefan
>
>
>
>
>
> *From:* nhibernate-development@googlegroups.com [mailto:
> nhibernate-developm...@googlegroups.com] *On Behalf Of *Fabio Maulo
> *Sent:* Tuesday, November 23, 2010 1:35 PM
>
> *To:* nhibernate-development@googlegroups.com
> *Subject:* Re
For the breaking changes, I think they need to get in before release
assuming that there are no major issues with the patches. For the
rest, I like Patrick's idea of making it clear that the LINQ provider
is more beta than RTM and not the recommended query mechanism for this
release. Let people try
An example of commitment can be:
"I would mostly help with the LINQ provider giving more attention and
pertinent comments to the many issues we have and we will have over LINQ."
If it work for you then you are welcome.
The mayor rule is: nobody can commit something breaking an existing tests.
If
On Tue, Nov 23, 2010 at 11:00 AM, David Pfeffer wrote:
> Personally, if NH3 is released without the issues with the LINQ provider
> working, I'm going to have to keep my project using the trunk so that I can
> get at the LINQ bug fixes. Right now I have HQL scattered throughout my
> project, and
On Tue, Nov 23, 2010 at 8:33 AM, Richard Brown (gmail) <
fluke...@googlemail.com> wrote:
> > Patrick seems to be on it, so why don’t you show him some love?
> ... and we are awaiting Patrick’s response to the invite to become a
> committer.
>
>
I'd be happy to help as much as my time allows. :)
oups.com] On Behalf Of Fabio Maulo
Sent: Tuesday, November 23, 2010 1:35 PM
To: nhibernate-development@googlegroups.com
Subject: Re: [nhibernate-development] Re: NHibernate 3 and Linq Provider
>From my point of view Linq is just another way to query the DB using NH.
Linq is not more strongly typed
rnate-developm...@googlegroups.com] On Behalf Of Fabio Maulo
Sent: Tuesday, November 23, 2010 1:35 PM
To: nhibernate-development@googlegroups.com
Subject: Re: [nhibernate-development] Re: NHibernate 3 and Linq Provider
>From my point of view Linq is just another way to query the DB using NH.
Linq is
Personally, if NH3 is released without the issues with the LINQ provider
working, I'm going to have to keep my project using the trunk so that I can
get at the LINQ bug fixes. Right now I have HQL scattered throughout my
project, and I really want to replace all of the queries with LINQ so that I
c
>From my point of view Linq is just another way to query the DB using NH.
Linq is not more strongly typed than QueryOver and is not more easy to learn
than HQL.
"Strategically" Linq is important... a strategy for what ? a commercial plan
? a war ? a competition ?
We are at one year of NH2.1.2 wh
*On Behalf Of *Fabio Maulo
> *Sent:* Tuesday, November 23, 2010 4:08 AM
> *To:* nhibernate-development@googlegroups.com
> *Subject:* Re: [nhibernate-development] Re: NHibernate 3 and Linq Provider
>
>
>
> Patrick, what Julian said to you is not enough ?
>
> Are you loo
groups.com
[mailto:nhibernate-developm...@googlegroups.com] On Behalf Of Patrick Earl
Sent: Tuesday, November 23, 2010 3:17 AM
To: nhibernate-development@googlegroups.com
Subject: Re: [nhibernate-development] Re: NHibernate 3 and Linq Provider
Here's a breakdown of the JIRA issues for th
Maulo
Sent: Tuesday, November 23, 2010 4:08 AM
To: nhibernate-development@googlegroups.com
Subject: Re: [nhibernate-development] Re: NHibernate 3 and Linq Provider
Patrick, what Julian said to you is not enough ?
Are you looking for a specific commiter ?
Do you want become part of the team ?
--
>From the point of view of a new comer to NHibernate I could not agree
more with James and Patrick, the Linq provider is the way to go, it
should be given a high priority. I have been using the Linq provider
in a couple medium size projects this year and it really pays off
using it. It streamlined
Patrick, what Julian said to you is not enough ?
Are you looking for a specific commiter ?
Do you want become part of the team ?
--
Fabio Maulo
El 22/11/2010, a las 23:16, Patrick Earl escribió:
Here's a breakdown of the JIRA issues for the LINQ provider:
Things that will cause breaking chan
Here's a breakdown of the JIRA issues for the LINQ provider:
Things that will cause breaking changes (probably missed some, but these
were obvious):
2099 (arguable if it should be done)
2402
2412
Bugs:
7 with fixes
12 with tests and no fixes
14 with no tests and no fixes
Improvements:
4 with fix
Do you mean before 2010/12/04 ?
On Mon, Nov 22, 2010 at 2:27 PM, James Kovacs wrote:
> I can understand your point of view, Fabio, that NHibernate has 5
> other query mechanisms - many more mature - than the LINQ provider.
> The reality in the .NET space is that LINQ is king. The preferred
> quer
I can understand your point of view, Fabio, that NHibernate has 5
other query mechanisms - many more mature - than the LINQ provider.
The reality in the .NET space is that LINQ is king. The preferred
query mechanism for LINQ-to-SQL and EF are both LINQ. Look at the
uptake of LINQ-to-NHibernate even
I should have time to review your Linq patches this week...
On Nov 21, 1:33 am, Patrick Earl wrote:
> Hi all.
>
> While I'm thankful for all the work that was put into the Linq
> provider for this release, I'm rather disappointed in how the beta
> cycle has gone. We're facing release, and there
31 matches
Mail list logo
