TIMESTAMP confusion
Jan Eden <[email protected]>
| Newsgroups | gmane.comp.db.mysql.perl |
|---|---|
| Message-ID | <r02010400-1037-5A10AFC85FE711D99E6E000A959B4026@[192.168.2.101]> |
Hi, I maintain a database locally which is queried via a Perl script to generate my website. Now there is one field of the TIMESTAMP type which should reflect the respective page's last modification date. This works fine when the database is queried locally. But when I dump the database (using mysqldump), transfer it to my webserver and import the dump into the database on the server, some pages carry the correct timestamp, while others have the timestamp of the import. Why is that? The tables are all dropped and recreated prior to inserting the data. Now I could understand if all the pages get a new timestamp (i.e. if the current value is not honored at all), but some pages are not affected. Those pages still carry the timestamp from the time when I initially added the TIMESTAMP field to my database. Why should this timestamp be more sticky than others? Thanks, Jan -- How many Microsoft engineers does it take to screw in a lightbulb? None. They just redefine "dark" as the new standard. -- MySQL Perl Mailing List For list archives: http://lists.mysql.com/perl To unsubscribe: http://lists.mysql.com/[email protected]