Subject: Appreciation Rewards: Amazon Voucher

From: Cash Back Rewards <[email-masked]>
Date: Fri, 15 Aug 2014 15:21:38 -0700

Attn Atompub-archive,

Catch this Cash Back Special for Back to School

Enjoy Cash Back from Amazon.
=============================
- $50 is yours to Redeem - 

It's simple...

1) Redeem Here -> http://www.busdeerow.com/amazon/rewards/id3322.html

- Amazon Rewards
August 15, 2014

We hope you enjoyed these rewards from amazon.
To stop further rewards write "stop" to Member Update Systems_9167 ROAD 177_Oakwood, OH 45873
or visit http://www.busdeerow.com/3kkss.kko3

An important difference is that DATETIME represents a date (as found in a calendar) and a time (as can be observed on a wall clock), while TIMESTAMP represents a well defined point in time. This could be very important if your application handles time zones. How long ago was '2010-09-01 16:31:00'? It depends on what timezone you're in. For me it was just a few seconds ago, for you it may represent a time in the future. If I say 1283351460 seconds since '1970-01-01 00:00:00 UTC', you know exactly what point in time I talk about. (See Nir's excellent answer below). [Downside: valid range].   MattBianco Sep 1 '10 at 14:36
40	  	
Another one difference: queries with "native" datetime will not be cached, but queries with timestamp - will be.   OZ_ Apr 28 '11 at 17:37
3	  	
"Timestamps in MySQL generally used to track changes to records" Do not think that's a good answer. Timestamp are a lot more powerful and complicated than that as MattBianco and Nir sayd. Although, the second part of the answer is very good. It's true what blivet said, and is a good advise.   santiagobasulto May 16 '11 at 14:00 
4	  	
"and are updated every time the record is changed" Is this true? Timestamp fields are automatically updated to the current time whenever a row is changed?   chaiguy Mar 16 '12 at 16:42
3	  	
Also 1 important note, DATETIME and TIMESTAMP can use CURRENT_TIMESTAMP, NOW() respectfully as it's default value, but DATE for example can't, because it uses '0000-00-00' by default, so to solve that matter U should write Your own trigger to that table, to insert current date (without time) in the field/col with DATE mysql type.   zeusakm Oct 15 '12 at 19:13
1	  	
in response to @zeusakm, there is a limitation that only one timestamp column per table can have default current_timestamp setting.   Kinjal Dixit Nov 2 '12 at 4:43
  	  	
Yeap this is a pertinent remark and this feature logically fair, there is no need of others.   zeusakm Nov 6 '12 at 10:00
2	  	
@chaiguy - I can find no reference to this in the documentation, and testing with MySQL 5.5 shows that the TIMESTAMP column is not changed when I update a row.   David Harkness Jan 21 '13 at 17:49
@DavidHarkness: Documentation says "To specify automatic properties, use the DEFAULT CURRENT_TIMESTAMP and ON Plap - Thanks for the link.   David Harkness Feb 24 '13 at 2:07@OZ_: Of course queries with static DATETIME values will be cached by mysql. Queries involving NOW(), CURDATE() and similar functions will not be cached. You can cache all queries which contain only functions which return the same value for the same parameter every time.   Marki555 Sep 27 '13 at 13:32
1