What's does the future hold for Criteria API? The introduction of LINQ seems to make a large part of it obsolete, but I haven't really got that much experience with LINQ-to-NH yet. One thing I like from the Criteria API is that it's got compiletime checks, however, it's not of much use if your propertynames changes, but neither is HQL. In HQL there is the possibility of typing keywords wrong, which is what I see as the major benefit of using the Criteria API.
I guess that LINQ will take care of both? 2009/5/20 Fabio Maulo <[email protected]> > The reuse of metadata and some base class for SQL creation is something > obvious (at least obvious for who know NH design).The underlining > implementation is completely different even more now that we are using AST > for HQL. > > 2009/5/19 Dmitiry Nagirnyak <[email protected]> > >> So Criteria API and HQL have different implementations? >> I thought they reuse the same infrastructure for generating SQL, mapping >> entities etc. >> I believe it should be true but probably not fully. >> Am I right here? >> >> To choose "the right tool" we need to know what that tool can and cannot >> do. >> So maybe you, guys, would be able to show couple of samples of what HSQ >> and Criteria API can(not) do. >> >> Cheers. >> >> 2009/5/20 Fabio Maulo <[email protected]> >> >>> Criteria is for dynamic queries >>> HQL is for static queries >>> >> >> >> >> > > > -- > 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 -~----------~----~----~----~------~----~------~--~---
