Guess I have sent my request too soon ... For the record: I swapped the order of the module loading from __PACKAGE__->load_components(qw/Core InflateColumn::DateTime/); to: __PACKAGE__->load_components(qw/InflateColumn::DateTime Core/);
Done that, I got an exception saying that DateTime::Format::MySQL was missing. Easily solved. But I still don't understand why the order of the component loading seems to be irrelevant on the development server. Cheers, Marc On Sun, Apr 3, 2011 at 4:07 PM, Marc Logghe <[email protected]> wrote: > Hi all, > Does anybody have an idea what could cause a date field not being inflated > when fetched from the database ? > Thing is dat the code works perfectly on my development machine, e.g. the > date field is properly inflated to a DateTime object. When deployed on the > development server I end up with strings instead of DateTime objects. On > both machines, mysql is used for storage. > I don't receive any errors about deflation/inflation issues. > > Regards, > Marc > > dev server (proper inflation): > DBIx::Class $VERSION = '0.08126' > MySQL 5.0.51a > > production server (no inflation): > DBIx::Class $VERSION = '0.08127' > MySQL 5.0.32 > >
_______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
