One of my favorite features of Class::DBI is the ability to inflate/deflate fields into any object. For instance, your date or time columns can be expanded into DateTime objects. The snippet below creates a method which, when called with a column name, will expand that column into a DateTime object. It requires the DateTime::Format::DBI module and the DateTime::Format module for your database. Within your application, whatever date field you get out of the database will automagically become a DateTime instance.
package My::Database; # Main Class::DBI module
use base 'Class::DBI';
# Other Class::DBI code here
sub is_datetime
{
my $class = shift;
my $field = shift || return;
use DateTime::Format::DBI;
my $dtf = DateTime::Format::DBI->new( $class->db_Main );
$class->has_a( $field => 'DateTime',
inflate => sub { $dtf->parse_datetime( shift ) },
deflate => sub { $dtf->format_datetime( shift ) },
);
}
package My::Database::SomeTable;
use base 'My::Database';
# Other Class::DBI code here
__PACKAGE__->is_datetime( 'timestamp' );
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|