| Type | Bug | Status | tested | Date | 27-Jun-2009 10:17 |
|---|---|---|---|---|---|
| Version | alpha 62 | Category | n/a | Submitted by | meijeru |
| Platform | All | Severity | minor | Priority | normal |
| Summary | TIME and ZONE components of DATE! value set wrong for "date only" value |
|---|---|
| Description |
see code; I would have expected /time and /zone to give an error stating they are not set my analysis of the way date values are packed in bits suggests that there is a bit free for indicating "time not set" in the zone field there is also a free bit (unless we go to 15 minute resolution) see comments to #973 |
| Example code |
>> d: now/date == 27-Jun-2009 >> d/time == 27-Jun-2009 ; not even a valid time ;-) >> d/zone == 1:00 ; a valid zone, but should it have been set? |
| Assigned to | n/a | Fixed in | alpha 64 | Last Update | 29-Jun-2009 16:37 |
|---|
| Comments | |
|---|---|
|
(0001081)
BrianH 27-Jun-2009 19:18 |
Here's what I would expect:
>> d: now/date == 27-Jun-2009 >> d/time == 00:00:00 >> d/zone == 0:00 Default zeros, no errors, and be sure to do the 15-minute zone resolution in #973. |
|
(0001082)
Carl 28-Jun-2009 00:16 |
This is an interesting question.
In R2, d/time returned NONE. This allowed a program to determine if the time field was set. If we return 0:00, then there's no simple programmatic way to determine if the field is set. |
|
(0001083)
Carl 28-Jun-2009 00:19 |
The behavior is now defined as:
>> d: now/date == 27-Jun-2009 >> d/time == none >> d/zone == none |
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 29-Jun-2009 16:37 | BrianH | Status | Modified | built => tested |
| 28-Jun-2009 00:19 | carl | Fixedin | Modified | => alpha 64 |
| 28-Jun-2009 00:19 | carl | Status | Modified | reviewed => built |
| 28-Jun-2009 00:19 | carl | Comment : 0001083 | Added | - |
| 28-Jun-2009 00:16 | carl | Comment : 0001082 | Added | - |
| 27-Jun-2009 19:20 | BrianH | Summary | Modified | TIME and ZONE components of DATE! value set even for "date only" value => TIME and ZONE components of DATE! value set wrong for "date only" value |
| 27-Jun-2009 19:18 | BrianH | Description | Modified | - |
| 27-Jun-2009 19:18 | BrianH | Code | Modified | - |
| 27-Jun-2009 19:18 | BrianH | Status | Modified | submitted => reviewed |
| 27-Jun-2009 19:18 | BrianH | Comment : 0001081 | Added | - |
| 27-Jun-2009 10:17 | meijeru | Ticket | Added | - |