> > in fact most of them scare me a bit because I'm using assigned GUID's > and I see that you discourage this practice... I guess that all > already persisted entities are previously loaded but I clearly > identify from your replies that the tree entities construction in my > application has some flaws. >
I don't discourage it but it helps preventing this specific issue. If this really creates a performance issue in your application then redesigning this type of aggregates can possibly improve performance. The keys that are communicates out side of such a service don't change. > BTW if I use generated GUID like with comb strategy after every insert > NH will need to query again to retrieve this generated field and at > the end I will need another select for each insert. Right? > The comb strategy is when you don't use assigned keys. Such a strategy should not create roundtrips for key validation. Maybe I do not understand your question. Ramon -- 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.
