|
|
Posted by Dikkie Dik on 07/04/07 23:40
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
>
One "ugly hack" is to keep a small history of all request and keep
building it up until the commit comes. You could even show the steps in
the history this way. This history can be kept in a separate table if
soliddb library supports more than one connection. (the second
connection is used so you can do a rollback in the first one)
Just play the entire history with each request and end it with a
rollback after reading the intermediary results. Only the commit request
should not do a rollback.
Best regards
Navigation:
[Reply to this message]
|