Brian Curley wrote:
> In reading through the code as a non-C kind of guy, it looks like there's an
> array of columnar values lumped together as old.* and new.* would need them,
> but nothing that contains the individual field or column names.
I'm not sure I understand. A
On 1 Oct 2010, at 4:44pm, Brian Curley wrote:
> My business case would be in the realm of logging, for example. If I'm
> using an audit-centric trigger, I'd probably want to store field and value,
Don't forget that one 'UPDATE' command can result in many different fields
being changed. So
Looking for some guidance or enlightenment on the available fields within a
given trigger.
In reading through the code as a non-C kind of guy, it looks like there's an
array of columnar values lumped together as old.* and new.* would need them,
but nothing that contains the individual field or
3 matches
Mail list logo