On Mon 20 Jan 2003 17:34, John Siracusa <[EMAIL PROTECTED]> wrote: > If so, I hope we can hammer out a spec quickly and get the ball rolling, > while also pursing long-term integration with the [EMAIL PROTECTED] folks. > There is a tremendous amount of low-hanging fruit in this area, IMO. Date > and time column types tend to have very regular formats, making them easy to > parse and easy to create. > > If we do the spec right, we won't have to change anything if/when the new > DateTime modules have stabilized. And in the meantime, DBI users everywhere > can stop dealing with date and time columns the same way they've stopped > dealing with manually quoting literals via s/'/''/g or s/'/\\'/ or whatever. > > So, what do you all think? :)
That is an extensive piece of reading. Seeing the subject I was affraid it would all end up again in making the braindead american date format to be default for DBI, but I soon realized this is a much higher approach. I think it is worth the effort to start it, but for starters you could check if we can use already installed Date:: modules like ::Parser, ::Calc, or ::Manip FWIW *if* there should be a default date format for DBI, *please* make it universal: YYYYMMDD and not MMDDYYYY or MM/DD/YYYY, because you have no idea how much irritation this arouses in European countries. date YYYYMMDD time HHMMSS datetime YYYYMMDD HHMMSS timestamp ssssssssss Note that there are /no/ seperators, this - again - to prevent confusion > -John -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.8.0 & 633 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro & WinCE 2.11 often with Tk800.024 &/| DBD-Unify ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
