Can you put your use case on the wiki? It would be helpful to start a
page about transaction use cases and where they are appropriate and
the downsides of using them. I'm thinking add something to describes
you use case and how it works (or doesn't work) with the current
model, and also the conflict checking transaction model. We might
figure out new solutions, tweaked models, etc that work better, or we
might see the pressing need for the transaction style.
-Damien
On Mar 25, 2009, at 4:52 PM, Tim Parkin wrote:
> Damien Katz wrote:
>
>> You could help by updating the wiki documentation to make this
>> clearer.
>> Multiple places if necessary.
>>
>
> Hi Damien,
>
> Could you help by taking a look at the issue I'm trying to work
> around.
> I'd love to work out a way of dealing with this without having to
> patch
> CouchDB (which is not what I want to do at all). I just think it's an
> important issues..
>
> Let me know if you want me to summarise it.
>
> Cheers
>
> Tim