Thanks guys

Being more comfortable with SQL, I think a trigger is more up my alley.

Will get back to you with sample code for others to use, when (if?) I
have a solution.

So, a trigger's the way go.

Found a pretty nice article:
http://joegornick.com/2009/12/30/mys...d-date-fields/

Still no luck Should be as easy as:

-- 1) create the columns
ALTER TABLE articles add `date_created` TIMESTAMP NULL DEFAULT NULL;
ALTER TABLE articles add `date_modified` TIMESTAMP NOT NULL DEFAULT
CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP;


-- 1) create the trigger

DROP FUNCTION IF EXISTS temp_before_insert_created_date ;
DELIMITER |

CREATE TRIGGER temp_before_insert_created_date BEFORE INSERT ON `articles`
FOR EACH ROW
BEGIN SET NEW.date_created= CURRENT_TIMESTAMP;

END


New rows get the same date_created and date_modified.

Edited rows remain the same.

Perhaps seeing when an article was last edited isn't all that important :/

ThomasH wrote:

"Does not work" is not an error description. Try to track the problem down
before you post, like reviewing the log. And get a real name.

You can add two (or more) columns in one ALTER statement, you know.

Wrong event for your purpose, yes?

RTFM: <http://dev.mysql.com/doc/refman/5.5/en/create-trigger.html>

HTH

--
PointedEars

Please do not Cc: me. / Bitte keine Kopien per E-Mail.

On Thu, 22 Sep 2011 19:23:38 +0200, ThomasH wrote:
Swap 'em. Put the one you want to auto-update as the FIRST timestamp in
the table. See if that works better.

--
96. My door mechanisms will be designed so that blasting the control
panel on the outside seals the door and blasting the control panel
on the inside opens the door, not vice versa.
--Peter Anspach's list of things to do as an Evil Overlord