Re: Re: new type proposal

From: "Dan Wilson" <phpPgAdmin(at)acucore(dot)com>
To: "Martin A(dot) Marques" <martin(at)math(dot)unl(dot)edu(dot)ar>, "Joseph Shraibman" <jks(at)selectacast(dot)net>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Re: new type proposal
Date: 2001-02-06 22:38:41
Message-ID: 009701c0908d$8e195ff0$533987cf@corp.peoplesoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

: El Mar 06 Feb 2001 18:54, Dan Wilson escribió:
: > I think these are vital! I was looking for something like this a few
: > months ago and was frustrated that I had to create a trigger to
accomplish
: > this... I know, I'm lazy. But if it were built in, I think it would be
a
: > big bonus!
:
: Not at all. It would be a step back. What your asking for already exists,
and
: any ANSI-SQL book will tell you to do it with a trigger.
: So wake up, don't be lazy, and CREATE those TRIGGERS!!!
:
: Saludos... ;-)

I disagree!

What would this do that would be non-standard? Does the SERIAL datatype add
something that is not standard? No... it just allows for an easy way to
implement something that is standard. The SERIAL "type" isn't really a
datatype, it's just a keyword that allows you to automatically specify an
int4 column with a related sequence and default. I don't see why the same
thing couldn't be done with TIMESTAMP!

I'm not saying to create an actual datatype that is called TIMESTAMP or
LAST_MODIFIED, just use it in a create script. It would then be implemented
with the DATE datatype combined with triggers.

Makes perfect sense to me!

-Dan

BTW: I'm completely awake and I build applications specifically so I don't
have to do things by hand (ie. so I can be "lazy" or more efficient,
whichever you prefer).

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alex Pilosov 2001-02-06 22:49:51 Re: Re: new type proposal
Previous Message os390 ibmos 2001-02-06 22:32:09 running a Terabyte sizedata warehouse using postgress