RE: datetime field

From: a_blonde@mindless.com > > ---- you wrote: > > Jonathan pointed out to me offline that there's something called > > DBINFO("utc_current") that might offer a solution. <Sigh> Guess I have>to > > read a manual again... > >Yes Dude, because that is in seconds, so you need to do something like: > >SELECT DATETIME(1970-01-01 00:00:00) YEAR TO SECOND + >DBINFO("utc_current") UNITS SECOND >FROM systables >WHERE tabid = 1> > > But it does beg the question: if there *is* a way of doing it, why >doesn't > > CURRENT work as expected? > >I think a stored procedure is seen as an object. An object can be timed, >but outside the actual object. The timex command is very good for this. It's all a question of perception, isn't it? :-) Anyway, the timex command is a crap choice because it's not as widely ported as you might expect. :-( "time" seems to be more universally ported, but even then, the format isn't standard -- RedTwat leading from the left, for example. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com