Powerhouse - Allbase problem

[Michael Lee]

I stand corrected :-).

Michael Lee
MCL Systems Inc.


"Fry, Mark" wrote:

> Hi Andreas,
>
> SET LOCK RECORD UPDATE in QTP has the same meaning as COMMIT AT UPDATE, so a
> commit is done at the end of every add, update or delete.  This means that
> effectively you have lost your rollback capability, since every add, update
> or delete is done within a separate transaction.  SET LOCK RECORD UPDATE
> also means that QTP is using the concurrency model, which utilises "Read
> Committed" transactions with Allbase, so for every update or delete, QTP has
> to perform a checksum validation to ensure that the row has not changed
> since it was read.  This can slow things down a bit.
>
> Best regards,
>
> Mark Fry
> Mark.Fry@Cognos.com
>
>                 -----Original Message-----
>                 From:   Noack, Andreas M.
> [mailto:Andreas.Noack@BetzDearborn.com]
>                 Sent:   20 May 1999 11:28
>                 To:     POWERH-L@lists.swau.edu
>                 Subject:        RE: Powerhouse - Allbase problem
>
>                 Hallo Jeff and all,
>
>                 thanks for the quick reply. The solution seems to work, but
> we are now
>                 afraid of follow-up problems. Having the default "lock file"
> we were always
>                 sure that no commit was done if e.g. step 1 of the QTP
> succeeded, but step 2
>                 failed. The rollback then always brought back the state
> before the QTP. If
>                 we now set "lock record" what will be the behaviour in this
> case? Can we
>                 also trust in a rollback for both steps or are actions from
> step 1 already
>                 committed? Thanks again for pointing out.
>
>                 Kind regards
>                 Andreas Noack
>                 BetzDearborn
>                 A division of Hercules Inc.
>                 Development Group Europe
>                 Tel. : +32.16.395.290
>                 Fax : +32.16.395.368
>
>                 The opinions expressed above are my very own. Due to this
> fact they may
>                 change anytime without further notice.
>
>
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> This list is closed, thus to post to the list, you must be a subscriber.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.