On Jan 14, 12:26 am, Fabio Maulo <[email protected]> wrote: > and a roundtrip with a select and an INSERT without a Commit of the UoW is > smarter than a roundtrip with a select ? > how much smart is that select ? > what will happen with the second Add ? (with the current behaviour you will > have *zero* roundtrip and no insert until UoW commit)
I get your point on "smart" being subject / dependent of the task to be solved. However, from reading the docs, it was my impression that lazy=extra was a hint to NH saying "do not fetch this collection unless you absolutely need to". Given such hint, I think it would be reasonable for NH to perform the uniqueness test (which is needed by the set but not the bag) within the database. Maybe I have misunderstood the purpose/scope of lazy=extra? I will be happy to contribute my proposal as an official feature request - possibly with a patch attached - if you believe there is a chance that it will be accepted.
-- 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.
