On Mon, May 19, 2014 at 12:29 PM, Dimitry Sibiryakov <s...@ibphoenix.com>wrote:

> :
> > Can you explain "erase in place" briefly?
>
>    I simply call update_in_place() with delete stub from VIO_erase() if
> the head record
> version is marked with the same transaction number. I.e. the same logic
> used as in
> VIO_modify(). It is undone as usual with VIO_backout().
>

To restate, if one transaction first creates a version of a record then
deletes it, you handle
it the same way you would a transaction that created a record version then
updated it - without
declaring any savepoints.

If a transaction deletes a record in which the latest version was created
by a different transaction,
you create a separate deleted stub, just as before.

Right?

Cheers,

Ann

>
> --
>    WBR, SD.
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> Firebird-Devel mailing list, web interface at
> https://lists.sourceforge.net/lists/listinfo/firebird-devel
>
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to