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

Re: Use of 'now'

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Vince Vielhaber <vev(at)michvhf(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Use of 'now'
Date: 2001-11-14 14:11:05
Message-ID: 3BF27B79.3F28F6D3@fourpalms.org (view raw or flat)
Thread:
Lists: pgsql-docspgsql-hackers
...
> template1=# insert into dd (y) values (1);
> template1=# select * from dd;
>     x    | y
> ---------+---
>  current | 1
> Must be since 7.0.3?

Prior to 7.2 (and up to two months ago -- ?? haven't checked the dates)
'current' was stored as a special value. It was only evaluated as the
current transaction time when math or some other transformation was
involved.

The feature dates from sometime after 1987 and sometime before 1995
(back when gods roamed the earth, etc etc).

Regarding the TIME data type: there was never a reserved value defined
for that type, so the feature was never available for it. Since
'current' and 'now' are synonymous, it is a one-liner to add recognition
of 'current' to that type. I've got patches...

                        - Thomas

In response to

Responses

pgsql-docs by date

Next:From: Bruce MomjianDate: 2001-11-14 16:10:14
Subject: Re: Use of 'now'
Previous:From: Vince VielhaberDate: 2001-11-14 10:59:46
Subject: Re: Use of 'now'

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-11-14 16:10:14
Subject: Re: Use of 'now'
Previous:From: Thomas LockhartDate: 2001-11-14 14:00:35
Subject: Re: 7.2b2 problem using like 'XXX%' sequential scan

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