Re: I was spoiled by the MySQL timestamp field

From: dev(at)archonet(dot)com
To: "Alan T(dot) Miller" <amiller(at)hollywood101(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: I was spoiled by the MySQL timestamp field
Date: 2003-01-23 17:48:17
Message-ID: 2942.192.168.1.16.1043344097.squirrel@mainbox.archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> As someone who is just getting started with PostygreSQL from years working
> with MySQL, it appears that the timestamp data type does not behave in the
> way it did with MySQL.

Much as I like MySQL, it can sometimes be a little *too* helpful.

> I got used to just defining a column as a timestamp
> and letting the database throw the latest time stamp in there whenever a
> row
> was updated. Is there anything simular in PosgreSQL?

When you create the table do something like:

CREATE TABLE foo (
bar timestamp DEFAULT now(),
...
);

You can of course do this with any column-type and value. See the
SQL-reference for details.

- Richard Huxton

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message will trillich 2003-01-23 17:48:27 Re: HOW-TO do incomplete dates: year, optional month, optional day?
Previous Message Renê Salomão 2003-01-23 17:29:35 Pg 7.3.1 & DBD::Pg 1.21