From: Eric B. <er...@go...> - 2005-08-29 11:38:56
|
Colin Paul Adams wrote: >>>>>>"Eric" == Eric Bezault <er...@go...> writes: >>>>> > > Eric> Colin Paul Adams wrote: > >> >> >> Is it OK to add is/as_fixed_offset to DT_TIME_ZONE, so as > >> to >> be >> able to access feature fixed_offset without an > >> assignment >> >> attempt? > Eric> It depends on what you want to use it for. In the > Eric> DT_ZONED_DATE_TIME you can get the fixed_offset using: > Eric> time_zone.offset (date_time) > >> >> But then I need to supply a date-time. > Eric> That's the `date_time' of the DT_ZONED_DATE_TIME. > >> Fine, if it's a zoned date-time, but not if it's a zoned date > >> (which it is). > > Eric> create my_date_time.make_from_date (d1.date) assert > Eric> ("+00:00 is UTC", d1.time_zone.offset (my_date_time).hour = > Eric> 0) > > So create a dummy date-time in order to get the (potentially variable) > offset of that dummy date-time in the current time zone, when what I > actually want is the offset from UTC of that time zone, which is known > to be fixed? > This seems perverse to me. Hmmm, isn't a potentially variable offset which is known to be fixed ... fixed?! Moreover the date-time provided is not arbitrary. If I remember correctly we once said that a zoned date was considered to be taken at midnight. If this is not the case, then DT_ZONED_DATE (and DT_ZONED_TIME) looks meaningless to me and only DT_ZONED_DATE_TIME makes sense to me. Now, if you said that you know that the time zone has a fixed offset, then what you probably want to have is DT_FIXED_OFFSET_ZONED_DATE (and the other variants for TIME and DATE_TIME). In fact, I can imagine what DT_FIXED_OFFSET_ZONED_TIME represents, but I'm still clueless as to what DT_ZONED_TIME is supposed to mean. -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |