I'm using MySQL which stores dates in ISO YYYY-MM-DD format but my users will expect to see dates as DD/MM/YYYY. They should be able to use 2 digit years for input, or leave it out all together. My Class::DBI objects have date fields which need to be checked and converted on input and reformatted on output.
There seems to be several ways to do this, which is better and why?

• Inflation and deflation with has_a? I think I'd need my own date class to stringify.
• Input goes via normalization, validation and constraints. What should go into normalization and what in a constraint?
• Is reformating output possible without has_a? Override the accessor?

Brad

---

---

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.