Re: default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP - Mailing list pgsql-novice

From Michael Fuhr
Subject Re: default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP
Date
Msg-id 20060124215006.GA91642@winnie.fuhr.org
Whole thread Raw
In response to Re: default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP  (f g <fg0fg1@yahoo.fr>)
List pgsql-novice
On Mon, Jan 23, 2006 at 06:24:43PM +0100, f g wrote:
> it seems a big montain just for that

Not really -- it's just that MySQL has a shortcut for a particular
special case and PostgreSQL has a more powerful generalized mechanism
(as does MySQL 5.0 with its "rudimentary triggers").

> plus had to do
> (shell) createlang -d [db] plpgsql

That's because PL/pgSQL isn't installed by default unless you've
created it in your template database.

> and replace $$ by simple quote

Dollar quotes are available in PostgreSQL 8.0 and later; if you're
running an earlier version then you'll have to use single quotes.

> and do you know why timestamp is only date instead of
> date+time ?

Timestamps contain both date and time.  Can you show an example of
what you're doing to get only dates?

--
Michael Fuhr

pgsql-novice by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: pl/pgsql switch
Next
From: Jaime Casanova
Date:
Subject: Re: block transactions in stored procedures