Jon Jensen wrote:
(1) It modifies the row before it's ever written to disk, instead of doing a separate UPDATE, and so is more efficient -- almost no impact.
Yeah, that's going to help.
(2) It uses the wallclock time instead of the start of transaction time, which may not matter much for sessions, but can be nice when making numerous updates in longer-running transactions, to see the order of operations. (Other times you may want the start of transaction time instead; it just depends on the circumstance.)
We're not going to need such fine granularity, but it won't do any harm.
Yep. We were originally doing other things in other places with the same trigger, but have moved those elsewhere now.When using this function, your trigger should fire *before*, not *after*
Doug -- Doug Whiteley, Web and Database Developer Scotweb Marketing Ltd Tel: 0131 510 0006 Fax: 0870 706 4938 suppressed http://www.scotweb.co.uk _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.