Re: [xml-dev] Transaction-safe XML-CLOB Update

Martin,

triggers are always part of the current transaction (i.e. you can't <commit> or
<rollback> in a trigger). However, if you would like an independent transaction
from your trigger, you can always use an autonomous procedure call (check Oracle
documention on this matter).

Cheers,
Jurgen.

Martin Bernauer wrote:

Martin Bernauer wrote:

> I wonder whether is it possible to update an XML document that is stored in
> a RDBMS in an attribute of type CLOB in a transaction safe way?
>
> Consider the following example: Upon an SQL-Insert into relation R (occuring
> in a transaction t) a trigger is fired (in the same transaction) that
> updates an XML Document stored as an attribute of type CLOB in relation S.
> When t
> is aborted (i.e., a rollback takes place) I do not want the update that the
> trigger performed on the XML document to be persistent.
>
> Is it possible to write the trigger, i.e. the XML document update, in a
> transaction safe way in general (independent of the employed DBMS)? However,
> I
> assume that it is only possible knowing the employed database. Since we use
> Oracle, does anybody know how I can achieve this in Oracle9i?
>
> Any help is highly appreciated.
>
> Kind regards,
> Martin Bernauer
>
> --
> GMX - Die Kommunikationsplattform im Internet.
> http://www.gmx.net
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>