[mythtv] database schema
mikej at carmelfly.com
Sat Mar 15 01:54:05 EST 2003
Hmm.. well it depends on what the intention of the field is...
>From the MySQL site:
-- SNIP --
The TIMESTAMP column type provides a type that you can use to
automatically mark INSERT or UPDATE operations with the current date and
time. If you have multiple TIMESTAMP columns, only the first one is
-- SNIP --
If this is what you are going for, then a timestamp is good, if you DO
NOT want the field to auto-update when the fields is updated or
inserted, then you MUST use a DATETIME...
To which portion of the SQL Schema are you refering?
On Fri, 2003-03-14 at 17:58, Matt Zimmerman wrote:
> On Fri, Mar 14, 2003 at 03:11:28AM -0800, Chris Palmer wrote:
> > I was wondering if there was a reason that the
> > TIMESTAMP field type was used instead of the
> > DATETIME field type for all the time/date fields.
> > Some things could probably be simplified if all
> > of those fields were of type DATETIME instead of
> > TIMESTAMP.
> I believe that all of the TIMESTAMP fields currently in the schema would
> make more sense as DATETIME fields. This sounds like a good candidate for
> some post-0.8 cleanup if you would like to send a patch.
More information about the mythtv-dev