[Seaside] Omnibase transactions and Seaside transactions

[Avi Bryant]

On Fri, 5 Jul 2002, Cees de Groot wrote:

> With this example, that leaves one problem: when getting back from the
> edit, you want to refresh the list; therefore, after the
> #callPage:/isolate# are done, you need to invalidate the current
> transaction and setup a fresh one so that the next time the whole list
> of items is rendered, the updates from the database are shown.
>
> Is it possible to switch transactions on-the-fly?

IASession>>currentTransaction: should work ok.  Or
IASession>popTransaction followed by IASession>>pushTransaction (note two
things - first, popping a transaction doesn't close it, which is
presumably what you want, and second, that it will complain if you try to
pop the very top transaction, so make sure that you push a transaction at
the start of your app).

Is all of this ReusableRef and invalidating transaction stuff just par for
the course when using OmniBase?  It all sounds rather messy...

Cheers,
Avi