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

[Michael Dean]

On Tue, 2003-06-10 at 15:47, Chris Weiss wrote:
> 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.

The MSSQL timestamp doesn't really represent time either.  It is meant
to be a guaranteed unique value for each row in a table.  To get a
usable timestamp, you have to use datetime.

PostgreSQL's timestamp was pretty much a datetime type.  It has been
deprecated in 7.3 (as I'm sure you know ;-)

Mike