A disconnected scenario is where I fetch some object graph from LLBLGenPro, disconnect from the session (and database connection), do some changes in the object graph (deleting in collections, adding entities, updating entities) and then reconnect and save....

Does LLBLGenPro support this kind of scenarios ?

LLBLGen Pro is working in a disconnected fashion.

Please the documentation's section: Concepts -> Stateless persistence

Walaa wrote:

LLBLGen Pro is working in a disconnected fashion.

Please the documentation's section: Concepts -> Stateless persistence

I read the section too, but I wasn't really sure. You are relying on the concurrency system then ?

Let say you have this scenario: userA has a snapshot of an object tree at 12:00 and another userB take the same snapshot at 12.01. UserA updates the object tree at 12.02 and userB updates at 12.03 while userB had the object tree still in memory(not having the updates from userA).... What will be the outcome here?

It depends on what you want the outcome to be. The default is that whoever updates last will win. But if you don't want this to happen, you can control itby using Concurrency predicates.

Walaa wrote:

It depends on what you want the outcome to be. The default is that whoever updates last will win. But if you don't want this to happen, you can control itby using Concurrency predicates.

oke, thanks!