pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jose' Soares Da Silva <sferac@bo.nettuno.it>
To: Hannu <hannu@trust.ee>
Cc: Byron Nikolaidis <byronn@insightdist.com>
Cc: interfaces postgres <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
Date: Thu, 11 Jun 1998 11:41:24 +0000 (UTC)
Message-ID: <Pine.LNX.3.96.980611112320.3708A-100000@proxy> (raw)
In-Reply-To: <357F9271.D4F12B47@trust.ee>

On Thu, 11 Jun 1998, Hannu wrote:

> Byron Nikolaidis wrote:
> > 
> > Krasnow, Greg wrote:
> > 
> > > I haven't looked at DATETIME stuff, but does Postgres not have something
> > > similar to Oracle's SYSDATE?  In Oracle you can set an Oracle DATE column to
> > > have a default of SYSDATE.  This way Oracle can fill in the column at the
> > > time an insert is done.
> > >
> > 
> > Yes, you are right, and I noticed Jose' earlier mail about this on the 'sql'
> > list.
> > 
> > If you do:
> > 
> > create table x (a timestamp DEFAULT CURRENT_TIMESTAMP, b varchar);
> > 
> > It works AND it puts in the current time at INSERT of the new row.  (I noticed
> > if you use CURRENT_TIME instead, you get the time you created the table at, for
> > every row, which is not very useful.)
> > 
> > The only problem is that it doesn't change the value on an UPDATE!
> > 
> > Any thoughts?
> 
> Why not use the system column tmin for this purpose?
> 
> hannu=> create table test(i int);
> CREATE
> hannu=> insert into test values(5);
> INSERT 17454 1
> hannu=> select tmin,tmax,i from test;
> tmin                         |tmax   |i
> -----------------------------+-------+-
> Thu Jun 11 11:12:17 1998 EEST|current|5
> (1 row)
> 
> hannu=> update test set i=2;
> UPDATE 1
> hannu=> select tmin,tmax,i from test;
> tmin                         |tmax   |i
> -----------------------------+-------+-
> Thu Jun 11 11:13:00 1998 EEST|current|2
> (1 row)
> 
> ------
> Hannu
> 
One minute! what's that tmin?
What version do you have?
I have v6.3.2 and it doesn't know tmin.

prova=> create table test(i int);
CREATE
prova=> insert into test values(5);
INSERT 15650 1
prova=> select tmin,tmax,i from test;
ERROR:  attribute 'tmin' not found
                                                            Jose'




view thread (27+ messages)  latest in thread

Message-ID: <Pine.LNX.3.96.980611112320.3708A-100000@proxy>
Permalink:  ../Pine.LNX.3.96.980611112320.3708A-100000@proxy/
Also on:    postgresql.org/message-id/Pine.LNX.3.96.980611112320.3708A-100000@proxy

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-interfaces@postgresql.org
  Cc: sferac@bo.nettuno.it, hannu@trust.ee, byronn@insightdist.com
  Subject: Re: [INTERFACES] Re: M$-Access'97 and TIMESTAMPs
  In-Reply-To: <Pine.LNX.3.96.980611112320.3708A-100000@proxy>
  References: <357F9271.D4F12B47@trust.ee> <Pine.LNX.3.96.980611112320.3708A-100000@proxy>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox