Subject | Re: [Firebird-devel] external data sources |
---|---|
Author | Jim Starkey |
Post date | 2004-04-29T17:12:02Z |
Roman Rokytskyy wrote:
external transactions. In many cases, the external system may not
support transaction or may have a model that doesn't integrate well, but
in most cases, unified transactions are straightforward and natural.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376
>It is clear to me that the mechanism should be beefed up to support
>External procedures described in that document cannot be used for such
>purposes, because current document does not allow procedures actively
>participate in deciding the transaction outcome, in other words, currently
>procedure interface does not have methods to tell server if "prepare"
>succeeded, and to be notified about either "commit" or "rollback" decision.
>This limitation does not allow procedure to start some tx on remote host,
>prepare it in prepare phase and commit or rollback it in the second phase of
>2PC.
>
>So, either concept of external procedures should be extended, or some other
>mechanism should be invented.
>
>
>
external transactions. In many cases, the external system may not
support transaction or may have a model that doesn't integrate well, but
in most cases, unified transactions are straightforward and natural.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376