Hi Arman, 1 - A proxy is really a word talks for itsself, when you request for an object NH (and some other platforms) gives you not the actual type, but a type inheriting from that. You are not effected because it is transparent for you, and that new type can be used by NH to perform things like lazy loading (load when/if a property is accessed).
2 - I prefer not to use anything related to OO, or ORM with my complex reports. Sometimes I am lazy and for easy/simple reports I use the entities given by NH, but beyond that I don't find HQL particularly good for complex querying, since its main intent is not that and you may want to use complex Dialect-specific structs within your query. On Tue, Apr 7, 2009 at 10:13 AM, Arman <arman.naj...@gmail.com> wrote: > > hi , > > as i am working with nhibernate for more than 2 year , but i have 2 > simple questions yet, > > 1- what a proxy is ? what i think is that a proxy is something like > watcher that when i want to access that object the proxy understand > and fetch that object from database at that time, it maybe useful for > performance in loading relations or objects . but i dont know if i'm > correct or not > > > 2- as you know in some reports , we want to get a complicated and > complex and heavy query , my question is , which one is better in > these situations? HQL or native SQL ? > if your answer is SQL , can i write my query in hql and get it's sql > translate and then run sql for get more quick results ?? > > thank U All, > > > > > -- Sidar Ok http://www.sidarok.com http://www.twitter.com/sidarok --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to nhusers@googlegroups.com To unsubscribe from this group, send email to nhusers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
