Hi Nando,


Answer inline:

> -----Original Message-----
> From: Nando Dessena [mailto:nandod@...]
> Sent: Wednesday, November 21, 2001 5:27 PM
>
> Paulo,
>
> > I find such feature very handy and flexible.
>
> I fear we are just trying to substitute a flexible approach we already
> have with something less useful (if also less tedious to implement, I
> admit).

As Artur already remarked, it is a time saver. That is what is handy about
it.

And it is good is it is flexible because that way one can use it to save
time in more situations.

> Should that define a system trigger?

Probably. That is an "implementation detail". We are still talking about
what the feature should be.

> Should that trigger fire before or after the user defined triggers?

It should be after all the other "BEFORE INSERT" (and maybe even "BEFORE
UPDATE")user defined triggers.

User triggers acting before the generator can analyze the input from the
client and have the ultimate decision on what value goes on in such field.
After the generator there would be no way of finding out if the value had
been filled in by the client or by the generator.

Notice that I am considering that, has it was proposed, the value would
only be generated for null valued fields.

> Should the user defined triggers be able to see/modify the value?

Obviously - from the previous answer - yes.

> ____
> _/\/ando

Have fun,
Paulo Gaspar


http://www.krankikom.de
http://www.ruhronline.de