++ed by:

132 PAUSE users
129 non-PAUSE users.

Peter Rabbitson 🐟‍👂
and 1 contributors


DBIx::Class::InflateColumn::DateTime - Auto-create DateTime objects from date and datetime columns.


Load this component and then declare one or more columns to be of the datetime, timestamp or date datatype.

  package Event;
  __PACKAGE__->load_components(qw/InflateColumn::DateTime Core/);
    starts_when => { data_type => 'datetime' }

NOTE: You must load InflateColumn::DateTime before Core. See DBIx::Class::Manual::Component for details.

Then you can treat the specified column as a DateTime object.

  print "This event starts the month of ".

If you want to set a specific timezone and locale for that field, use:

    starts_when => { data_type => 'datetime', extra => { timezone => "America/Chicago", locale => "de_DE" } }

If you want to inflate no matter what data_type your column is, use inflate_datetime or inflate_date:

    starts_when => { data_type => 'varchar', inflate_datetime => 1 }
    starts_when => { data_type => 'varchar', inflate_date => 1 }

It's also possible to explicitly skip inflation:

    starts_when => { data_type => 'datetime', inflate_datetime => 0 }


This module figures out the type of DateTime::Format::* class to inflate/deflate with based on the type of DBIx::Class::Storage::DBI::* that you are using. If you switch from one database to a different one your code should continue to work without modification (though note that this feature is new as of 0.07, so it may not be perfect yet - bug reports to the list very much welcome).

For more help with using components, see "USING" in DBIx::Class::Manual::Component.


Chains with the "register_column" in DBIx::Class::Row method, and sets up datetime columns appropriately. This would not normally be directly called by end users.

In the case of an invalid date, DateTime will throw an exception. To bypass these exceptions and just have the inflation return undef, use the datetime_undef_if_invalid option in the column info:

        data_type => "datetime",
        default_value => '0000-00-00',
        is_nullable => 1,
        datetime_undef_if_invalid => 1


If you have a datetime column with the timezone extra setting, and subsenquently create/update this column with a DateTime object in the DateTime::TimeZone::Floating timezone, you will get a warning (as there is a very good chance this will not have the result you expect). For example:

    starts_when => { data_type => 'datetime', extra => { timezone => "America/Chicago" } }

  my $event = $schema->resultset('EventTZ')->create({
    starts_at => DateTime->new(year=>2007, month=>12, day=>31, ),

The warning can be avoided in several ways:

Fix your broken code

When calling set_time_zone on a Floating DateTime object, the timezone is simply set to the requested value, and no time conversion takes place. It is always a good idea to be supply explicit times to the database:

  my $event = $schema->resultset('EventTZ')->create({
    starts_at => DateTime->new(year=>2007, month=>12, day=>31, time_zone => "America/Chicago" ),
Suppress the check on per-column basis
    starts_when => { data_type => 'datetime', extra => { timezone => "America/Chicago", floating_tz_ok => 1 } }
Suppress the check globally

Set the environment variable DBIC_FLOATING_TZ_OK to some true value.


More information about the add_columns method, and column metadata, can be found in the documentation for DBIx::Class::ResultSource.
Further discussion of problems inherent to the Floating timezone: Floating DateTimes and $dt->set_time_zone


Matt S. Trout <mst@shadowcatsystems.co.uk>


Aran Deltac <bluefeet@cpan.org>


You may distribute this code under the same terms as Perl itself.