Oh, I guess I should have mentioned this on the list and not just in the bug:
I would like core developers to take a look before 1.1, because, as the
solution I propose involves adding a new settings knob (and possible
behavior), it is borderline between bugfix and feature. Way closer to bugfix
Hi list,
Responding to Jacob's message of yesterday, I worked a little more on this
issue, and brought my patch to a working state, tests included. This revealed
some issues with my approach, which I've documented on the patch.
I would like to see this resolved for 1.1, either way.
On Monday
On Sunday 08 March 2009, Malcolm Tredinnick wrote:
> On Sat, 2009-03-07 at 21:24 +0200, Shai Berger wrote:
> > Hi list, Malcolm,
> >
> > If I start working on a patch for #9664 (Transaction middleware closes
> > the transaction only when it's marked as dirty; marked for milestone
> > 1.1), will I
On Sat, 2009-03-07 at 21:24 +0200, Shai Berger wrote:
> Hi list, Malcolm,
>
> If I start working on a patch for #9664 (Transaction middleware closes the
> transaction only when it's marked as dirty; marked for milestone 1.1), will I
> be duplicating effort?
>
> The solution I would propose is,
Hi list, Malcolm,
If I start working on a patch for #9664 (Transaction middleware closes the
transaction only when it's marked as dirty; marked for milestone 1.1), will I
be duplicating effort?
The solution I would propose is, essentially, a removal of the clean/dirty
concept from transaction
