Hello Lester,

> >>>I fail to see what this has to do with the TIME datatype?
> >>
> >>This was proof of TIME is not meaning of real-time.
> >>There is no real-time. Using of meridian is not must.
> >>Lets make a techo fantasy..
> >>You are going to Mars' office department of Upscene.
> >>What TIME system will you use and store to TIME field in there?
> >>Will you use mars merdians?(i am sure there must be a greenwich of
> >>GB)
> >>Or are you say: hey TIME type is incompatable for here, we need a
> >>new datatype for Mars.
> >
> > The TIME datatype is valid for our little planet only.
>
> Actually since time is stored as a fraction of a day, then the Mars
> version would be a fraction of the Mars day, and you just change the
> display functions.

;-)

I kinda meant the restrictions it has -- 60 minutes per hour, 24 hours
etc...

> I use TIME for hours and minutes and cast to TIME when I want to display
> a duration as hours and minutes. Days just being multiples of 24 hours (
> or what ever you want for the Martian clock ;) )

But not a duration > 24 hours, I guess? As you are misusing the type... but
you
know it ;)

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com