Description: ------------ When user notes in the manual are approved, the timestamp is updated. This is a problem e.g. on the following page: http://pear.php.net/manual/en/package.fileformats.spreadsheet-excel-writer.spreadsheet-excel-writer-worksheet.writestring.php The user submitted his note two days before (May 28th), Craig answered it in a new note (but didn't approve the original note) on May 30th. Now I have approved the note, and the timestamp was updated. Unfortunately, the order of the two notes is now wrong. (Not really a problem here, but with more notes on the page, the right order would be more helpful.)

Here's the problem, someone snuck in a ON UPDATE CURRENT_TIMESTAMP for the note_time field yet it's not in the sql / xml files for pearweb. Now we have to wait for some sys admin to remove that from manual_notes.

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.

This is not fixed in the database, the timestamp is still updated to the current time.

Dang, that's weird, I'll try to look into this before the next release.

still in the database.

This needs to fixed by somebody that has access to the PEAR database. Greg or Martin, can you please look into the database and fix this problem? (This is currently the last open problem scheduled for the next release of pearweb.)

Thank you for your bug report. This issue has been fixed in the latest released version of the package, which you can download at http://pear.php.net/get/pearweb

Re-opening, as this is still not fixed.

Then the issue is something else than in the database, Greg did a alter statement on that field and even showed me so we've be sure nothing went wrong in that. I guess someone has to comb that note class David wrote.

> Then the issue is something else than in the database, > Greg did a alter statement on that field and even showed > me so we've be sure nothing went wrong in that. I tried it in my local installation: I've approved an unapproved note from somewhere in December. The timestamp remained the same. In the notes class there is no UPDATE SQL query that changes the note_time field. This field is only used in SELECT and INSERT queries. Therefore, this still seems to be an issue in the database. Greg, did you modify the right table? It's manual_notes, not just notes.

Greg changed the database field to datetime like you suggested, could you recheck ?

Perfect, it works now. The timestamp doesn't get updated anymore.