> > > Core devs: > Any reason not to use database transactions to make sure we don't end > up with incomplete/corrupted data? I don't have any evidence that > would have saved my bacon in this particular case. But in the process > of investigating I noticed how many complex views there are creating > several different types of objects in one go but are not wrapped in a > transaction. > >
Losing data or having data in an inconsistent state is certainly very bad. In general, transactions would make sense but as you mention it will be hard to verify that more explicit transaction management would fix the issue. So, to answer your question, forking and starting a branch with improved transaction management would be fine. I would just want to make sure we're smart about where it's used and not just using the shotgun approach to trying to solve the problem. -Chris -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
