I find the whole thing brilliantly elegant and practical and
easy to use and... what can I say more to encourage some one
to implement it?
=:oD

Have fun,
Paulo Gaspar

> -----Original Message-----
> From: Paul Schmidt [mailto:paul@...]
> Sent: Thursday, November 22, 2001 3:50 PM
>
> ..................
>
> Actually I think Jason was right on the ball, if the value has been
> "preset" by the application, then we assume that the application
> knew what it was doing, and accept that value. I also agree with
> Jason that the RETURNING clause has a lot of merit, especially
> since the mechanics are already in the engine.
>
> I think that we need to put as much into SQL as possble, not
> everyone knows the API, nor do they want to know the API.
> However RETURNING should return all values after the relevent
> triggers have fired (before and after insert triggers) so if you have a
> field affected by triggers you could use the RETURNING values to
> update the display. Also RETURNING should be independant of
> the actual inserted fields, so if you have a value calculated in a
> trigger you can return that value as part of the insert.
>
> Paul