John Peacock [EMAIL PROTECTED] wrote:
Dave Rolsky wrote:
- Work with just dates and do date math on them (at the level of days,
months years).
I think I was one of the ones advocating for a way to do this [...]
I second this. I'm not sure how much you work with SQL, but the standard
On Fri, 17 Jun 2005, Jonathan Leffler wrote:
DATE has components from year down to day; TIME has components from hour
down to microseconds (or finer); and TIMESTAMP contains components from
How can you have a time with a time zone when it has no date? Weirdness.
I would certainly like to
On Thu, 16 Jun 2005, Yitzchak Scott-Thoennes wrote:
On Wed, Jun 15, 2005 at 02:17:29PM -0500, Dave Rolsky wrote:
- Work with just dates and do date math on them (at the level of days,
months years). The current implementation is quite broken for this
purpose, because when you assign a
So there's been a bunch of date math + TZ related bugs lately in
DateTime.pm, and more to be resolved.
I think the fundamental problem is that DateTime.pm is trying to cover a
few too many bases in one simple API.
There are a bunch of things people would like to be able to do:
- Work with
Dave Rolsky wrote:
- Work with just dates and do date math on them (at the level of days,
months years).
I think I was one of the ones advocating for a way to do this, since in
a business environment, the time is frequently not important (for
example number of days between order and
On 6/15/05, Dave Rolsky [EMAIL PROTECTED] wrote:
Also, I think we may need to consider serious backwards incompatibility in
the future of DateTime.pm (possibly via a new namespace like DateTime2) to
really clean this up, but that'll wait til I'm less tired ;)
Just break it. DateTime's nowhere
John Peacock wrote:
and at any point in that sequence, allow the user to set the value to
undef (for I don't have any information about anything below this).
All math operations would then stop at the point where either term (for
binary operations) contained an undef (hence two disimilarly
