It's not illogical at all. You often want (sometimes need) that field to make sure a record has not changed when you go back to update the row. MS Access (and others) uses this so as not to overwrite changes made since the record was retrieved. You can't always rely on the client to set field=NOW(), and it makes for that much less coding.
mysql, query j----- k----- On Friday 05 April 2002 07:53, Hihn Jason wrote: > Yes I did, but it is very long, and it was very long ago. > Could someone please explain to me why this was done? It seems more > confusing to do this than to not do this. Why when you can just say "SET > field=NOW()" in the update statement would anyone build this auto update > of timestamps in? (the kicker is you HAVE to do it for all timestamps in > a schema past the first) Additionally, what if I wanted the time stamp > format (without formatting (spaces, colons, and dashes)) (which I do) > > A very illogical feature I must say... Anyone agree with me? > (Forgive me Rick, I didn't hit "reply to all") -- Joshua Kugler, Information Services Director Associated Students of the University of Alaska Fairbanks [EMAIL PROTECTED], 907-474-7601 --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
