Re: [Phpgroupware-developers] Re: timestamps with my MySQL in schema_proc

[Chris Weiss]

mysql only updates the first one, and doesn't allow null in any of them.  in
comparison, mssql only allows one per table and auto updated it with each 
update to
the row, doesn't allow defaults, and seems to allow null's, though it probably
tosses in the current timestamp no matter what.  I don't know that pg does but I
suspect it'll be yet another set of rules.

address@hidden wrote:
>
>"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
>
>
>_______________________________________________
>Phpgroupware-developers mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>