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.
Bu
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 w
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.
Isn't there an access to the old values?
What about inserting the values again which are deleted?
Greetings
Georg
Zabach, Elke wrote:
Georg Thome wrote:
Georg Thome wrote:
>
> If I understand you right, you want to preserve the data of one row
> being changed after insertion.
> I think the only way for doing this is via triggers.
> You have to implement a BEFORE UPDATE and a BEFORE DELETE trigger on
> that table.
Nice idea, but MaxDB does not
If I understand you right, you want to preserve the data of one row
being changed after insertion.
I think the only way for doing this is via triggers.
You have to implement a BEFORE UPDATE and a BEFORE DELETE trigger on
that table.
Georg
Nick Chan wrote:
hi
is there a way to make data in a fiel
Nick Chan wrote:
is there a way to make data in a field read-only after first time being added/set ?
Grant the SELECT, INSERT (and possible DELETE) privileges on the table,
but for the UPDATE privilege use only a subset of columns:
http://www.sapdb.org/7.4/htmhelp/48/f0dac7225811d3a97d00a0c9449261
