Posted by Mariano Montone on 07/04/07 21:30

On 4 jul, 17:52, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> Mariano Montone wrote:
> > Hi,
> > I'd like to know how I can achieve keeping a transaction live
> > across multiple http requests. This is not for production work so any
> > ugly hacks are welcomed. My idea is using solidDB engine optimistic
> > concurrency control for transactions in order to avoid locking. Isn't
> > there any way I can keep the transaction id or something in order to
> > have access to the same transaction later on?
>
> > Thanks, Mariano
>
> You can't. Connections are closed at the end of each page.
>
> You wouldn't want to, anyway. It's NEVER a good idea to hold any kind
> of lock (even ones implicitly held in transactions) across user input.

I know it's not a good idea. That's why I want to do some tests
involving optimistic concurrency control provided by solidDB. That
means that there's no locking. Transactions are validated on commit
instead.

Mariano

[Back to original message]