Hi John, I recently scanned the code to get an idea of the changes necessary to implement a basic conflict resolution at least on time stamps.
The code to delete back then AFAIR did not check if SQL-delete was successful. If my visualization was correct, any rowlock could then probably be problematic, as the biz layer would be out of synch with the backend. I did not check if exeptions were raised if/when delete from DABO fails due to rows locked, which I could have done via backend interface... regards thomas John Fabiani schrieb: > Hi Guys, > > I like to know the thinking on row locking within the context of the Dabo > framework. We all realize that in some cases it is not desirable to have > optimistic locking (or the MVCC locking of Postgres). For example > shipping/closing a sales order but allowing a second user to modify the same > sales order at the same time. > > To my knowledge Dabo does not provide any tools to assist with pessimistic > locking. So I wonder if there have been any discussions on row locking etc.. > > Of course Postgres also makes the problem a little more complex due the > different "select" modes (select for update, etc..). > > Of course general thoughts etc. are more than welcome. > > Johnf > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users > Searchable Archives: http://leafe.com/archives/search/dabo-users > This message: > http://leafe.com/archives/byMID/[email protected] > > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
