> I would be inclined to disagree. Why do the databases job? Simply set a
> datetime field to default to getdate() when inserting a new field, and
> Whenever you do and update to the database set your datetime field to
> getdate() again.
One possible problem arises with this - if the date/time are different from
the database server compared to the web server - if the date is completely
wrong then this will royally mess up - otherwise I'd say to use this rather
than let CF do the work - but I always use an Identity field whenever I use
a time-stamp, just because I'm paranoid <g>
Philip Arnold
Director
Certified ColdFusion Developer
ASP Multimedia Limited
T: +44 (0)20 8680 1133
"Websites for the real world"
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
