Peronsally, I do CreateODBCDateTime just so I can see everything going in, and just leave the database to be my bucket.
Chad who uses a bucket when seasick On 8/17/05, Scott Thornton <[EMAIL PROTECTED]> wrote: > Hi, > > If it is just one field on the table, the default value is okay... but if you > intend to have more than one field effected by trigger-like actions, it may > be better if they were all in the one place... ie the Insert trigger, rather > than having default values specified in DDL. > > Cheers, > > >>> [EMAIL PROTECTED] 08/17/05 9:13 am >>> > Heya all, > > What might be a purely academic question here... if you want a record to > automatically have a 'date created' field. Is it best practise to achieve > this by giving the 'dateCreated' field a default value of getdate(), or write > a trigger on INSERT that sets the 'dateCreated' field. Is there any reason to > do one or the other? > > bye! > > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia > Developers: http://lists.daemon.com.au/ > > > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
