[mythtv] database schema

Mike Javorski mikej at carmelfly.com
Sat Mar 15 22:44:20 EST 2003


Well not wanting to step on your toes Isaac, but I see two items on this
issue worth commenting on:

 - TIMESTAMP is limited to POST 1970 & PRE 2037 dates. Granted the 2037
limit isn't an issue, but if we were to (eventually) indicate things
like original air date of a show (such as Dick Van Dyke or Scooby-Doo,
both of which were made in the 60's), the system would go foo-bar on the
dates.

- As far as size is concerned, its really at the "microscopic level" in
this instance.. I mean 8 BYTES vs. 4. We aren't talking a HUGE deal
(considering most of us run machines with more than enough space).

Anyway.. if I get some time, I will look around and maybe send you an
"all-encompassing" patch (that updates everything that needn't be a
timestamp to be a datetime, and adjust the SQL queries accordingly) for
your approval. Def. going to be for post-.80 (don't want to slow the
release down if I can avoid it)

- Mike


On Sat, 2003-03-15 at 21:05, Isaac Richards wrote:
> On Saturday 15 March 2003 06:51 am, Chris Palmer wrote:
> > My guess is that when the schema was first designed, that it
> > was assumed that the TIMESTAMP datatype was the proper type
> > based solely on its name.  As a datatype it is interchangeable
> > with the DATETIME field, but it has other specific built-in
> > functionality which makes it useful for logging/tracking of
> > database updates.
> 
> I chose the timestamp datatype because I liked its storage format more, and 
> it's half the size of the datetime datatype.  Modification to the records in 
> question rarely happens, so I figured it wasn't that big of a deal.
> 
> Isaac
> 
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-dev



More information about the mythtv-dev mailing list