Bug #138
xsd:date with zero offset conflicts with dates that have no TimeZone
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
fixed
Description
Adding the literal "2006-08-23+00:00"^^xsd:date or "2006-08-23"^^xsd:date works in isolation (time-zone preserved). However, if they are both added to Mulgara only the first value is preserved. If a date is first added without a timezone than Mulgara will not preserve a zero offset timezone for that date.
Updated by Paula Gearon over 15 years ago
The problem here is the comparator, which only looks at the value, and not the representation. This particular problem can be fixed by having the comparator look at ALL the data, and not just the value portion. This means that the values can no longer be considered the same (and hence, cannot be joined on), though that may be acceptable.
Updated by Paula Gearon over 15 years ago
- Status changed from New to Closed
- Resolution set to fixed
Updated by Paula Gearon over 15 years ago
- Status changed from Closed to Feedback
- Resolution deleted (
fixed)
Comparator update was not enough
Updated by Paula Gearon over 15 years ago
- Status changed from Feedback to Closed
- Resolution set to fixed