My issue is that I have customizable tables that I'm trying to handle generically and I wanted to avoid having to treat date columns differently. Either by calling methods or writing wrappers. I want the mutator to accept D/M/Y strings, even sloppy ones. Given all this, is has_a still what I'm after? Or is changing the accessor/mutator? (Or may I should just change my requirements)
Also, this was partly an exercise in understanding Class::DBI for me. I didn't expect the inflate method to be used via the mutator.
Thanks a lot anyway,
Brad
PS.You could probably write a custom module that inherits from Time::Piece::MySQL.
Note that Time::Piece::MySQL
doesn't actually inherit from Time::Piece. Time::Piece is
a difficult base class.
In reply to Re: Re: Re: Re: Date conversion with Class::DBI
by bsb
in thread Date conversion with Class::DBI
by bsb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |