I may be getting this all wrong but here's my reasoning:

• has_a sets triggers to inflate a value to an object on both 'select' and 'after_set_$column'.
• The inflate method converts the nugget of data into an object.
• In the 'select' case, the nugget comes from the database.
• In the 'after_set_$col' case, the nugget comes from the user

I want to use different formats for the user and the database. Maybe has_a could be part of the solution in combination with normalization (which happens prior to 'after_set_$col' and can do format conversion). But like I said, I don't think has_a alone is enough. I'd like to be wrong though.

I found the docs quite confusing on this, even more so after I started trying to do it.

The better answer seems to be just to override the accessor/mutator and leave the objects data in the MySQL format. The outside world sees it d/m/y and Class::DBI can ignore it. I should also be able to override all 'date' type accessors during class initialization automatically.

(I'm not sure if this will play well with validation though).

sub gp_ref_date {
    my $self = shift;
    if(@_) { # setting
        my $date = shift;
        if($date =~ m! (\d+) / (\d+) (?:/ (\d+) )+!x) {
            my $y = $3;
            $y += ($y < 70) ? 2000 : 1900 if($y < 100);
            $date = sprintf "%4d-%02d-%02d", $y,$2,$1;
        }
        return $self->_gp_ref_date_accessor($date);
    } else {
        my $date = $self->_gp_ref_date_accessor(@_);
        $date =~ s!(\d{4})-(\d\d)-(\d\d)!$3/$2/$1!;
        return $date;
    }
}
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.