On Thu, 2003-01-23 at 16:35, Dave Rolsky wrote:
On Wed, 22 Jan 2003, David H. Lynch Jr. wrote:
You're confusing phsyical with logical. A given DBMS may _store_ dates as
julian days (or MJD, or whatever) and you'd never know, since you only
deal with the representation of the date (as a
On Wed, 2003-01-22 at 18:09, David H. Lynch Jr. wrote:
I have always had a particular affection for Dates as Julian day
numbers the number of days since .
They are really easy to manipulate, compare, Virtually all the
nasty aspects of dates become a function of the routines
On Wed, 22 Jan 2003, David H. Lynch Jr. wrote:
I have always had a particular affection for Dates as Julian day
numbers the number of days since .
They are really easy to manipulate, compare, Virtually all the
nasty aspects of dates become a function of the routines for
: Tuesday, January 21, 2003 1:34 PM
To: Dave Rolsky
Cc: John Siracusa; DBI Dev
Subject: Re: Integrating date and time parsing and formatting
Let me put in a plug for separate DATE and DATETIME types. I don't know
whether the datetime list has discussed this, and the last time I tried
to join
On Tue, 21 Jan 2003, John Siracusa wrote:
On 1/21/03 3:38 AM, H.Merijn Brand wrote:
FWIW *if* there should be a default date format for DBI, *please* make it
universal: MMDD and not MMDD or MM/DD/, because you have no idea
how much irritation this arouses in European countries.
On 1/21/03 11:04 AM, John Siracusa wrote:
On 1/21/03 10:52 AM, Matt Sergeant wrote:
Does this cover DBD's (like mine) that don't support *any* data types?
Sure. If you really make no distinctions about data types, then you'd
probably just make the methods no-op pass-throughs for the data.
On Tue, 21 Jan 2003, John Siracusa wrote:
On 1/21/03 3:38 AM, H.Merijn Brand wrote:
FWIW *if* there should be a default date format for DBI, *please* make it
universal: MMDD and not MMDD or MM/DD/, because you have no idea
how much irritation this arouses in European countries.
On Tue, 21 Jan 2003 [EMAIL PROTECTED] wrote:
Let me put in a plug for separate DATE and DATETIME types. I don't know
whether the datetime list has discussed this, and the last time I tried to
join the list, I kept getting some weird error.
Dates are like the integers. Datetimes are like
On Tue, 21 Jan 2003, Dave Rolsky wrote:
This should probably be discussed on the DateTime.pm list.
Uh, that'd be [EMAIL PROTECTED] There is no DateTime.pm list. I'm
losing my mind.
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
the difficulty when times are involved.
Thanks
-John
Dave Rolsky [EMAIL PROTECTED] on 01/21/2003 01:14:02 PM
To:John Siracusa [EMAIL PROTECTED]
cc:DBI Dev [EMAIL PROTECTED] (bcc: John Tobey/Intdata)
Subject:Re: Integrating date and time parsing and formatting
On Tue, 21 Jan 2003, John
FWIW *if* there should be a default date format for DBI, *please* ...
*If* there should be a default date format for DBI it will be the ISO
standard used by ODBC.
For typed placeholders:
$sth-bind_param(1, 2002-01-21, SQL_DATE);
$sth-bind_param(2, 17:45:23, SQL_TIME);
$sth-bind_param(3,
On Tue, 21 Jan 2003, Tim Bunce wrote:
FWIW *if* there should be a default date format for DBI, *please* ...
*If* there should be a default date format for DBI it will be the ISO
standard used by ODBC.
I think there may be some confusion here.
What _I_ had envisioned, if this were to come
On Tuesday, January 21, 2003, at 02:06 PM, Tim Bunce wrote:
I'm not keen on having the DBI or drivers call methods
when passed blessed references.
I'd say the object should stringify to the standard ISO format
or the uer calls the method explicitly:
$sth-bind_params(1,
On Tue, 2003-01-21 at 14:25, David Wheeler wrote:
Also, I'd love to get fetch() and such to optionally turn date and time
and datetime fields into objects before returning them, too. Would such
a thing be possible?
Sybase::CTlib and Sybase::DBlib can do this - optionally creating a
DateTime
On Tuesday, January 21, 2003, at 02:34 PM, Michael Peppler wrote:
Sybase::CTlib and Sybase::DBlib can do this - optionally creating a
DateTime object that is in native Sybase format and can be cracked and
manipulated with the Sybase API. It works, but the object creation for
each fetched row is
The best thing about standards is there are so many to choose them, or
maybe it's that you don't really need to follow them (e.g., HTTP and
HTML). ISO 8601 requires date and time to be separated by a 'T':
1998-05-12T14:15Z.
Tom.
Tim Bunce [EMAIL PROTECTED] writes:
FWIW *if* there should be a
I just started reading about the new date and time module consolidation
project on the [EMAIL PROTECTED] mailing list. The subject of database-
specific date and time formats quickly appeared, mostly in the context of
how to expose this kind of functionality (a subclass for each database? DB
17 matches
Mail list logo
