On 1/18/03 7:21 PM, Dave Rolsky wrote: > On Sat, 18 Jan 2003, John Siracusa wrote: >> Just as an aside (or maybe not?) I've always wanted DB-specific date parsing >> and formatting functionality to hang off of the $dbh, just like quoting >> does. It's much easier to keep code database-neutral this way. >> >> Now each DBD could in turn use DateTime::Formatter::MySQL, >> DateTime::Parser::MySQL, and so on internally, but I don't want to see any >> of those class names in my code! :) > > That's a nice idea, but people may want to use these modules without using > DBI
And so they can. What's stopping them? > and I have no control over the DBI/DBD modules. No, but if you ask nicely... :) > Once the DateTime suite is more advanced, I'd be happy to work with Tim Bunce > and DBD module authors on integrating DateTime support into the DBI, if > there's interest from that group of folks. I'm thinking that asking sooner is better than asking later... >> Also remember that, for the purposes of databases, you'll have to deal with >> "odd" things like "-infinity" and "0000-00-00 00:00:00" which make most >> (all?) current date modules choke badly. > > Ah, SQL DBMS's are all so broken, ain't it just great? Indeed :) -John
