I don't prefer any of those methods because I didn't tried one of them :o) yet. I think I've missunderstood something in your last mail.
If the rollback works I would prefer this.
Zabach, Elke wrote:


Georg Thome wrote:

Uups
I didn't know the missing because I did not need them on SapDB/MaxDB.
But I did not understand why the after update trigger does not work.


If you CHECK the old value and then return an error, the trigger fails,
the update itself fails, leaving the values as they were.


Isn't there an access to the old values?


If you include an access to the old values, there is one in. There is no
implicit access to them.


What about inserting the values again which are deleted?


If you want to insert the row again by using every column-value (if you have
more than just a few columns....), it is possible, but why do you prefer this
to the rollback of the original delete?

Elke
SAP Labs Berlin

Georg
...

--
Georg Thom� IEE Luxembourg S.A.
IT dept. / software development / DB-administation
tel. 00352/7289896810 fax 00352/7289896109
www.iee.lu / [EMAIL PROTECTED]

This e-mail may contain trade secrets or privileged, undisclosed or
otherwise confidential information. If you are not the intended recipient
and have received this e-mail in error, you are hereby notified that any
review, copying or distribution of it is strictly prohibited. Please
inform us immediately and destroy the original transmittal from your
system. Thank you for your co-operation.


-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to