The main difference between LINQ and HQL is that HQL was designed to be translated to SQL. We have to design our systems to use the best query-tool for a specific task. I'm working with NH3 in production with more than one project using HQL, QueryOver, LINQ, H-SQL, SQL and even Criteria (variable no strongly typed queries). We don't have to limit our possibilities (EQO is with me ;) )
-- Fabio Maulo El 18/07/2010, a las 07:48, Richard Birkby <[email protected]> escribió: > On 18 Jul 2010, at 11:34, Frans Bouma <[email protected]> wrote: >> >> One could argue to always do an FKSide LEFT JOIN PKside, even if the >> fk side has no nullable fk fields, though it might be an RDBMS can >> optimize the INNER JOIN better than the LEFT JOIN. > > Yes - SQL compact will not rearrange tables in a queryplan when it has > an outer join. Ironically, i've used this fact to force a more optimal > queryplan by using an outer join in HQL. > > Richard
