Re: [Roundup-devel] Multi-request transactions

[Richard J. <ri...@bi...>]

On Tuesday 14 August 2001 06:07, Lennon Day-Reynolds wrote:
> Something else occurred to me while I was hacking at this over the
> weekend: it seems like the ideal place to store a transaction log would
> actually be in a user session, rather than in the central database log.
> Since we're already 'tagging' the journal of edits based on a username,
> why not simply use a session object to store changes, then commit or
> rollback by either flushing it to persistent storage, or simply deleting
> the session. This would have the advantage of allowing multi-form edits
> to occur in one 'transaction', and default the values of form fields to
> those most recently provided by the user.

Can you give an example of where a multi-form edit would be required in an 
issue tracker?

I can't think of an example where a database transaction spans more than one 
form, e-mail or command-line submission. I was thinking along the lines of a 
simple in-process log.


    Richard