We make use of LLBLgen for some years now, but most of the time the applications are used by one person. Now more users are working with the same application on the same database.

I'm not a expert on LLBLgen implementation, but I was wondering the following: Are during update of an Entity only the Dirty fields written?

Are there more design constraints to be take care of if LLBLgen is used in a multiuser environment?

We have LLBLGen Pro 3.5 Final (September 17th, 2012) Database is SQL servers: 2008 / 2012 / 2014

Meindert wrote:

I'm not a expert on LLBLgen implementation, but I was wondering the following: Are during update of an Entity only the Dirty fields written?

Only dirty fields are included in the update sql statement.

Meindert wrote:

Are there more design constraints to be take care of if LLBLgen is used in a multiuser environment?

Not exactly in LLBLGen but in client-server applications in general: concurrency. For more info see Concurrency Control in the documentation.