I'm wondering if anyone has done a change to lifecycle transitions to make 
them more robust.

Say for a case where you have 2 or more conflicting transitions from a 
single state.  If one or both take long enough to run, you can potentially 
run both transitions and end up with a weird unexpected state.

Ideally, you want to lock the record from other transitions occurring while 
one is in process.  I'm trying to think if there's a effective way to do it 
without adding an additional column and/or having multiple db calls per 
transition.

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/d/optout.

Reply via email to