Use DateTime objects uniformly, improve expires parsing

Always use DateTime objects for every date field in the database,
and translate them into the local time zone for display when
pulling them out of the database.  This should provide better
portability to different database backends.

Change the parsing of expires arguments to use Date::Parse, thus
supporting a much broader variety of possible date and time
formats and allowing easy conversion to a DateTime object.
Document the new dependency.

Change-Id: I2ee8eaa6aa6ae9925ac419e49234ec9880d4fe95
Reviewed-on: https://gerrit.stanford.edu/1555
Reviewed-by: Russ Allbery <rra@stanford.edu>
Tested-by: Russ Allbery <rra@stanford.edu>

1 files changed, 4 insertions, 3 deletions

diff --git a/README b/README
index 4c9f1d7..f32ba15 100644
--- a/README
+++ b/README
@@ -68,9 +68,10 @@ REQUIREMENTS
   plus Module::Build to build.  It uses DBIx::Class and DBI to talk to a
   database, and therefore the DBIx::Class and DBI modules (and their
   dependencies) and a DBD module for the database it will use must be
-  installed.  The DateTime module is required for date handling, and the
-  SQL::Translator Perl module is also required for schema deployment and
-  database upgrades.  You will also need the DateTime::Format::* module
+  installed.  The Date::Parse (part of the TimeDate distribution) and
+  DateTime modules are required for date handling, and the SQL::Translator
+  Perl module is also required for schema deployment and database
+  upgrades.  You will also need the DateTime::Format::* module
   corresponding to your DBD module (such as DateTime::Format::SQLite or
   DateTime::Format::PG).