This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients
Date 2004-05-03.17:46:40
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=31435

I don't understand what TimeFromTicks() is supposed to do.  
Seconds-from-the-epoch is a point in time, not a time-of-
day.  If some DB API requires guessing some transformation 
from seconds-from-the-epoch to time-of-day, that's fine, but 
it doesn't belong in Python's datetime module.

The datetime module should certainly have a method to 
construct a datetime.datetime from a seconds-from-the-
epoch argument -- seconds-from-the-epoch is a way of 
specifying a datetime.datetime.  Given that, if the intent is to 
throw away the datetime.date portion of the 
datetime.datetime object, retaining only the datetime.time 
portion, then that's trivially accomplished by invoking dt.time
() (where dt is the datetime.datetime object).

Do any databases really store time-of-day as a seconds-from-
the-epoch value?  Google's top hit on TimeFromTicks() today 
happens to be a msg from Anthony saying that Oracle does 
not.
History
Date User Action Args
2007-08-23 15:31:56adminlinkissue876130 messages
2007-08-23 15:31:56admincreate