maria-developers team mailing list archive

[worklog-noreply@xxxxxxxxxxxx]

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: ability to have multiple TIMESTAMP columns with CURRENT_TIMESTAMP /
		on_update TIMESTAMP
CREATION DATE..: Wed, 28 Sep 2011, 19:37
SUPERVISOR.....: 
IMPLEMENTOR....: 
COPIES TO......: 
CATEGORY.......: Client-BackLog
TASK ID........: 239 (http://askmonty.org/worklog/?tid=239)
VERSION........: Benchmarks-3.0
STATUS.........: Un-Assigned
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: 0 (hours remain)
ORIG. ESTIMATE.: 0

PROGRESS NOTES:



DESCRIPTION:

Let's say I have two columns: 'created' and 'updated'

Currently I can only let 'created' use the CURRENT_TIMESTAMP attribute.

But ideally, I'd like 'updated' to also use CURRENT_TIMESTAMP as well as on_update 
TIMESTAMP. This makes a lot more sense for operations like this when a developer 
would have 'created', 'updated', or even 'deleted', columns. Only way we can do 
this right now is via triggers or (shudder) setting them from the app server.

I understand there would be a underlying change and would really appreciate some 
kind of change for this particular behavior.


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v4.0.0)