I think it is important to know all APIS and know how to choose each one on the best scenario. For sample, I think LINQ is more productive for trivials queries, it i easy to write and works fine (improving the linq support and getting better on each new version of NH). For dynamic queries, QueryOver and Criteria can be the right choice, because they provide a best support to write dynamic statement, in additional to be easer than linq expressions tree. For sample, I have implemented a Kendo UI Grid server side support with QueryOver and it works perfectly, amazing job the NH development team have made with QueryOver. HQL is fine to write everything given it looks like SQL, and I enjoy writting non-default sql update, for sample: "update Entity set field=:fieldValue where code=:code and age > 0".
On Mon, Apr 2, 2018 at 7:40 AM, Ricardo Peres <[email protected]> wrote: > I'm very happy that it has so many querying options. There are things that > can only be expressed in either HQL or SQL, for example, query-only > properties. Plus the dynamic nature of strings lends itself much better to > some scenarios. > > RP > > -- > 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 https://groups.google.com/group/nhusers. > For more options, visit https://groups.google.com/d/optout. > -- ______________________________________ Felipe B Oriani [email protected] -- 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 https://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
