On Sun, Jan 06, 2002 at 11:57:58AM -0500, Marc Delisle wrote: 10 seconds remaining... -- _________________________________________________________________ Olivier Mueller - om(a)8304.ch - PGPkeyID: 0E84D2EA - Switzerland qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch

On Sun, Jan 06, 2002 at 07:54:46PM +0100, Olivier M. wrote: found the "problem" :) : ____________________________________________________________________________________________________________________ Revision 1.60 / (view) - annotate - [select for diffs] , Tue Nov 20 15:54:01 2001 UTC (6 weeks, 5 days ago) by loic1 Branch: MAIN Changes since 1.59: +6 -4 lines Diff to previous 1.59 set the default function to "NOW()" for timestamp fields only in insert mode (ie not in update mode) ____________________________________________________________________________________________________________________ well... would you mind if we turn this on again ? The default mysql behaviour (using the mysql client or scripts) is to update the ts in *any* case, so I think it would be better the way it was in version 1.59... As an example, on one of my servers, there are cronjob scripts watching for changes in an sql table: if a record changed (new timestamp), it would run some progs to update /etc/passwd etc... But if the timestamp is not updated, it won't work... and that is PMA's work :) cheers, Olivier -- _________________________________________________________________ Olivier Mueller - om(a)8304.ch - PGPkeyID: 0E84D2EA - Switzerland qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch