|
Hi, I've been reading up on DataObjects.Net in the Manual. I see that Entities are fully transactional objects, meaning one can only persist objects within a transaction, which is fine for batch runs. At page 71 of the Manual there is mention of Disconnected Operations. Since we are writing a WPF Program we don't want transactions to be open during editing by the user. We will be using Disconnected Entities which will be persisted at a later time (with concurrency handling and so on). When we want to implement this we will need a full description, on how to realize this, pretty soon. In the Manual this is missing at the moment. Can you provide us with a (draft) description? Regards Paul Sinnema Diartis AG Updated at 04.06.2010 13:22:44Thanks, I'll take a look Updated at 15.06.2010 9:54:30Hi Alex, Would you consider the following example a good practice with DO4? At the start of our Application we open a Domain and a Session. A DisconnectedState attaches to the Session During several minutes we allow the User to read, add, update and remove data At a certain moment (primarely when the users leaves the current screen) we persist the data to the DB This means that we keep a Domain, Session and DisconnectedState open for as long as the Program is running. Regards Paul Sinnema Diartis AG This thread was imported from our support forum. The original discussion may contain more detailed answer. |
Exactly - thanks a lot. There is also OrderAccounting sample in Sandbox, but it will be updated soon (current version isn't simple enough).
Yes, that's ok. But remember:
Likely, you'll need several Sessions & DisconnectedState. E.g. in MDI app.
You must balance between amount of consumed RAM and DisconnectedState lifetime, if you really frequently update it.
When you install latest official published version (4.2.1 or 4.3 RC2) than you find in start menu under "DataObjects..." folder, sample called "WPF Sample" which uses disconnected scenario you describe.