Skip site navigation (1) Skip section navigation (2)

Re: default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: f g <fg0fg1(at)yahoo(dot)fr>
Cc: pgsql-novice(at)postgresql(dot)org, andreas(dot)kretschmer(at)schollglas(dot)com
Subject: Re: default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP
Date: 2006-01-24 21:50:06
Message-ID: 20060124215006.GA91642@winnie.fuhr.org (view raw or flat)
Thread:
Lists: 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

In response to

pgsql-novice by date

Next:From: Jaime CasanovaDate: 2006-01-25 22:02:56
Subject: Re: block transactions in stored procedures
Previous:From: Michael FuhrDate: 2006-01-24 20:51:38
Subject: Re: pl/pgsql switch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group