On Dec 2, 2009, at 5:49 PM, Ian Kelly wrote: > On Wed, Dec 2, 2009 at 3:25 PM, Michael Bayer <mike...@zzzcomputing.com> > wrote: >> from the article: >> >> Beware while the TO_CHAR function works with both datatypes, the TRUNC >> function will not work with a datatype of TIMESTAMP. This is a clear >> indication that the use of TIMESTAMP datatype should explicitly be used for >> date and times where a difference in time is of utmost importance, such that >> Oracle won't even let you compare like values. >> >> this suggests to me that DATE is more of a general purpose date/time type >> whereas TIMESTAMP is specifically when you need granularity to compare the >> ordering of events down to the millisecond, with some loss in simplicity . > > This was fixed in version 9.2.0.3.0. Using that release or later, > TRUNC works just fine with TIMESTAMP. See the thread at > http://forums.oracle.com/forums/thread.jspa?threadID=372457 > > I should stress that I don't think using DATE is a problem so long as > there's a way to get TIMESTAMP instead. Especially if the goal is to > support Oracle 8i, where TIMESTAMP doesn't even exist.
TIMESTAMP is of course available, though I think in the interests of oracle tradition we should stick to DATE as the default for DateTime. TIMESTAMP suggests a specific use case to me, that of comparing the exact time of event occurence. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
