Re: After Insert Trigger

Leffler, Jonathan wrote: > JL: That on its own is not sufficient. You also have to ensure that the INSERT statement > does not specify the LastUpdated and ByWhom columns. This typically means either you > INSERT through a view which excludes those columns: > > CREATE VIEW ins_tablename (col1, ..., colN) AS > SELECT col1, ..., colN > FROM tablename;> > Note that colN excludes LastUpdated and ByWhom... Or you specify the column list in the > INSERT statement: > > INSERT INTO tablename(col1, ..., colN) > VALUES (val1, ..., valN);> > This allows the DEFAULT for the columns to take effect; if a value is specified for the column, > that value is inserted, regardless of the defaults. > > Uhmm, Hate to nitpick, but isn't that the prefered method of writing the inserts? (Like part of the recommended coding standards?) -Mikey -- #include <std_disclaimer.h> /* Mike Segel (MS385) */ #include <No_Spam.h> #ifdef OFFENDED_BY_CONTENT The author takes no responsibility for this post. Any resemblence to a coherent rational thought is purely coincidence. -The Management. #endif ***************************** Due to AGIS's Refusal to Act Responsibly We are blocking all of their domains at the packet level. This block will exist until AGIS modifies their policies to conform to existing RFCs and net community standards. We encourage all ISPs and domain holders to do the same. *****************************