That would depend on what the date was reflecting.
For example, in one of my databases, I have datetime fields which gets updated with the first and last time and date a cable modem was seen on the network. For this field, I used cmfirstseen and cmlastseen...which reads as "cable modem first seen" and "cable modem last seen".
Simply using the field name 'date' here, would not describe fully the use of that field. Even if there was only one field, say the last seen field, 'date' would not really tell me what the data in that column really represents.
I recommend using variable and field names which accurately represent the data contained therein while keeping the length to a minimum.
If you'd like to keep the date that a transaction was made, how about trans_date? If you'd like to keep track of the last time a credit card was used, how about cc_lastused? To keep track of the date the customer opened the account, how about account_created?
These are just a few examples based on the topic of your postings 🙂
Hope this helps.
-Rich