Drewes wrote:
I did a search on google and I guess the product you compare llblgen against is dataobjects.net from x-tensive.com.
Yes.
Drewes wrote:
From what I know about this product is that is determines at runtime what database it is running against.
Dataobjects.net takes full control of the schema and if it detects that the schema is behind the latest mapped entity definitions then it regenerates the schema from the entity class definitions.
Drewes wrote:
With LLBLgen the schema is analyzed before and the classes generated based on the schema information, so as a result there is no overhead at runtime, setting property values etc. will be just as fast and probably faster with llblgen. That, plus the other advantages of llblgen that you mention yourself make your decision on what product to chose an easy one I think.
Urmm you answered a different question. Yes it is true that the just in time schema updates and abstract class completions in DataObjects.Net is a performance hurdle in the code, compile, test cycle but my question relates to class property access performance.
Presumably LLBLgen intercepts write access to an entity property so that the entities it is managing in a session can be persisted automatically during some sort of session.Commit() operations? If so what are the performance implications of the LLBLgen interception design?