> > 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>
If you're using the date/time field as a timestamp to handle concurrency
issues, it doesn't matter what time the web server thinks it is! You simply
need to query the field before showing the update form to the user, then
query again to see whether anyone's changed the field since the user
selected that record to edit.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
