[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Phpgroupware-developers] Re: timestamps with my MySQL in schema_proc
From: |
totschnig . michael |
Subject: |
[Phpgroupware-developers] Re: timestamps with my MySQL in schema_proc |
Date: |
Tue, 10 Jun 2003 15:51:26 -0400 |
User-agent: |
Gnus/5.090007 (Oort Gnus v0.07) XEmacs/21.4 (Economic Science, i686-pc-linux) |
"Chris Weiss" <address@hidden> a écrit:
>>Also I am not convinced by the fact that multiple timestamps are
>>updated differently in MySQL and other databases, since normally why
>>would you need several *timestamps*, if all they tell you is when the
>>row was updated. In other words, I do not think, that the fact that a
>>data type behaves strangely in strange cases, should prevent us from
>>using it in the normal cases.
>
> some ppl like using timestamps for events, like "when it was closed" or "when
> the
> item shipped"
If I understand right, the point is that MySQL when you use multiple
timestamps, always updates all of them, and that other RDBMS let you
specify "Update timestamp 1, but leave timestamp 2 untouched". I
understand that this is a limitation, but I am not sure why this
should prevent me from using tables with one single timestamp field
with MySQL.
Michael