As [Ben][1] and [Nar][2] nicely explained, breaking down the date-time object into buckets of date and time parts would help detect seasonal trends, where the complete (and usually even worse - unique) date-time object would miss it

You didn't mention any specific machine learning algorithm you're interested in, but in case you're also interested with distance-based clustering, like k-means, I'd **generalize** the date-time object into the **unix-time format**.
This would allow for a simple numerical distance comparison for the algorithm, simply stating how far 2 date values are.

In your example I'd generalize the date-only value 2014-05-05 to 1399248000 (the unix time representing the start of may the 5th 2014, UTC).

[One could argue that you can achieve that by bucketing the date-time into every possible date-time part.. but that would significantly increase your dataset dimensions. So, I'd suggest combining the unix-time, for distance measuring, and some of the date-time buckets]


  [1]: https://datascience.stackexchange.com/questions/2368/machine-learning-features-engineering-from-date-time-data/#2370
  [2]: https://datascience.stackexchange.com/questions/2368/machine-learning-features-engineering-from-date-time-data/#2369