Yes, I know this approach, but this may bring about heavy text search while putting hint to the right place by table search/replace on the sql statement preparing.
Now we have a problem with every pre sql statement. - Define your Table aliases which will be marked hint - Search Sql string which started "SELECT" word. - Locate aliases/tables - Calculate text and find right place for put the hint - ready! In my opinion, This approach wouldn't work under large systems. That's why hints are should be written while query for the optimization. 24 Ağustos 2015 Pazartesi 14:25:35 UTC+3 tarihinde Gunnar Liljas yazdı: > > It's because NHibernate is not a data access library. It doesn't aim for > SQL completeness. > > To implement it, you could use an interceptor. > > > http://stackoverflow.com/questions/3584740/add-sql-query-options-to-nhibernate-query > > 2015-08-24 9:52 GMT+02:00 Oğuzhan Soykan <[email protected] > <javascript:>>: > >> What is the approach Nhibernate to this ? >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/nhusers. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
