Use DateTime objects in the database layer, not strings

Pass in DateTime objects for the date fields in the database instead
of formatted time strings.  This provides better compatibility with
different database engines.  Document in README the need to install
the DateTime::Format::* module corresponding to the DBD::* module used
for the server database.

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

1 files changed, 5 insertions, 4 deletions

diff --git a/README b/README
index ef910bd..4c9f1d7 100644
--- a/README
+++ b/README
@@ -68,10 +68,11 @@ 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 SQL::Translator Perl module is also required for schema
-  deployment and database upgrades.  If the wallet server is used with a
-  SQLite 3 database, the Perl module DateTime::Format::SQLite should also
-  be installed.
+  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
+  corresponding to your DBD module (such as DateTime::Format::SQLite or
+  DateTime::Format::PG).
 
   Currently, the server has only been tested against SQLite 3, MySQL 5,
   and PostgreSQL, and prebuilt SQL files (for database upgrades) are only