Re: Re: New SimpleORM Whitepaper

Hi,

I think I second that. Until recently I never had any problems, but a
few days ago, we had a deadlock detection under Postgresql after a code
refactoring. Using SOPTIMISTIC solved the issue, so I guess new default
mode would be fine.
That said, I think I will also have to make sure my code is able to
handle broken optiistic locks in a user friendly way...

Franck


Le mercredi 06 août 2008 à 11:55 +0000, hkara1 a écrit :
> --- In [email protected], Anthony Berglas <anthony@...> wrote:
> >
> > Over the last few days I have been completely reworking the white 
> > paper. And as I do so, I review the code and design and test 
> > cases. It is all looking quite good.
> > 
> > I am most of the way through it, and have attached the current 
> > version. Please read through it and tell me what you think. What's 
> > wrong, what's missing, what's superfluous.
> > 
> > It is currently checked in under 
> > simpleorm\trunk\simplewebapp\common\doc\simpleorm-webSite. (I need 
> > to reorganize this when we make the Franck branch the main 
> > branch.) I just edit it with Komposer, but any lightweight editor 
> > will do (not MS Word!).
> > 
> > The most substantial change to SimpleORM as a result of the review
> is 
> > changing the default locking mode from SFOR_UPDATE to 
> > SBASIC. Optimistic locking is always performed. This felt more 
> > natural to me, but maybe SFOR_UPDATE would be better given that it
> is 
> > mainly used for transactional processing. But we don't want to lock 
> > too much. Opinions welcome. We could also make the default mode 
> > settable on the session, but we really do not want too many modes
> and 
> > options -- hard to test etc.
> > 
> > Regards,
> > 
> > Anthony
> > 
> > Dr Anthony Berglas, anthony@... Mobile: +61 4 4838 8874
> > Just because it is possible to push twigs along the ground with ones
> nose
> > does not necessarily mean that is the best way to collect firewood.
> >
> 
> Hi,
> 
> I welcome this change; I am heavily using Oracle with SimpleOrm
> (storing and serving a few ten of thousands of biological results in 
> an 900 bed hospital), and every now and then, (once every month in
> average) Oracle entered in a deadlock. I resolved the problem by
> subclassing the Oracle driver and disabling locking, and then I
> used the modified driver.
> Otherwise SimpleOrm works quite well for me.
> 
> Best regards,
> 
> Harry
> 
> 
> 
> 
>  



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/SimpleORM/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/SimpleORM/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/