In my experience it's always best to convert dates and times to epochtime before storing in the DB. Then convert them to some other format when you want to use or display them. As your app grows you'll often find that you need more than one human-readable format, and if you are converting from one format to another at the app level, doing all the conversions from epoch time is easier. Also the dates/times can be sorted numerically.
Some would say you shouldn't be doing processing in your app that could be handled at the DB layer. Yes, it's true that your DB can handle dates, and probably even provides date/time functions. But you have Perl! Store the simplest representation of your data in the DB and do your processing in Perl, and you will die a happy monk.
Hope this helps!
The way forward always starts with a minimal test.