You mean in the global_detailed_data model definition, using date instead of timestamp for the field we’re defining as update_date? We considered that, I don’t see too much of a downside to storing the exact timestamp vs. a truncated calendar date because it can be truncated when you’re reading from the data later.
I guess the pro/con (could be viewed as either depending what you want to accomplish) would be that if you use a calendar date, if you scheduled archive to run 2x/day, but your update_date only changes once a day, then data would only be stored once a day.