On Nov 1, 2010, at 2:08 PM, Michael Hipp wrote: > On 11/1/2010 11:33 AM, Michael Bayer wrote: >> OK I think in this case, as in many others, is that "subtransactions" are >> not an easy to learn feature, hence it is controlled by a flag that is off >> by default. ... > > ... for features that aren't intended for typical use > > Then perhaps say that. "This is an advanced feature that will be of no > interest to most users - begin_nested() is a much better choice for nesting > of transactions."
Wouldn't you then ask, "if begin_nested() is so much better, why is subtransactions=True available?" In fact, one is not better than the other, they are for totally different use cases. The issue remains is that nesting of transactions is hard to explain, and whatever language I choose, no matter how much time I spend trying to tailor the language so that nobody misunderstands it, nobody is misconstruing its use, people will continue to misunderstand it. Since this thread is going on and on, of course I'm going to go rewrite the docs now. But come back in 6 months, someone else will misunderstand *that*, and have the same issue. This is why after many years of doing this I have become hesitant to react in the usual "Docs aren't clear to user, user gets an exception, user says the docs should be made specific to his or her specific misunderstanding" - its like whack a mole. No more discussion on this is needed. I will rewrite the docs now, thanks for your input. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
