On Monday, October 31, 2011 05:40:25 am Thomas Ganss wrote: > 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
In my case I'm using Postgres and have Advisory Locks available. I having been thinking I could use some/all of the bizObj.beforexxxx() hook methods to check on the advisory lock. That said I was hoping for more discussion on the matter because I know others must have similar needs of the Dabo framework. 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]
