So, how would you solve the use case I described? What
I need to do is to
perform some checks before calling WikiPage::doEdit, and make sure the
result of
the check is still valid when the actual save occurs.
SAVEPOINTs are basically nested transactions. Can you describe the use case
in more detail?
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com | tylerromeo(a)gmail.com
On Fri, Aug 24, 2012 at 12:36 PM, Daniel Kinzler <daniel(a)brightbyte.de>wrote;wrote:
> On 24.08.2012 03:14, Aaron Schulz wrote:
> > SAVEPOINTs are useful if we really need to support people rollback
> > transactions *and* we need nested transaction support. I think they
> could be
> > made to work, but I'm not sold on their necessity for any use cases we
> have.
>
So, how would you solve the use case I described? What
I need to do is to
perform some checks before calling WikiPage::doEdit, and make sure the
> result
of
the check is still valid when the actual save occurs.
>
> I can't see a clean way to do this without supporting nested transactions
> in
> *some* way.
>
> -- daniel
>
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
>
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>