From: Colin P. A. <co...@co...> - 2004-11-25 14:30:43
|
>>>>> "Colin" == Colin Paul Adams <co...@co...> writes: Franck> That's why I'm uncomfortable with the idea of Franck> DT_ZONED_DATE: - unlike all the other date types it's not Franck> cleanly comparable (DT_DATE don't overlap so remain Franck> comparable whether interpreted as a full day or as any Franck> point in the day) - unlike the other zoned types, you Franck> can't directly use the date with the zone (conversion must Franck> have a time). Colin> Well, I don't see partial ordering as an argument against Colin> the type. Franck> xml-schema 3.2.7.5 says: | dates without time zone have a Franck> total order among themselves. Franck> which hints that dates with TZ have only a partial order Franck> at best. Colin> I would say, at least, rather than at best. It depends upon Colin> the application. If you use DT_ZONED_DATE_TIME instead, Colin> then you are IMPOSING total ordering, which I would say Colin> prempts the application's perogative. Colin> But for sorting purposes, there IS a total ordering. Z Colin> clearly sorts earlier than +0100. Then it's up to the Colin> application to decide whether to successive dates having Colin> the same date part are to be considered equal or not. Can we come to some conclusion on this? I'm anxious to start coding soon, as at the moment, lack of date/time processing is a big hole in the XPath library. -- Colin Paul Adams Preston Lancashire |