| From: | Joseph Shraibman <jks(at)selectacast(dot)net> |
|---|---|
| To: | Tim Uckun <tim(at)diligence(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: new type proposal |
| Date: | 2001-02-06 23:06:50 |
| Message-ID: | 3A80838A.2AE5855F@selectacast.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tim Uckun wrote:
>
> At 03:43 PM 2/6/2001 -0500, Joseph Shraibman wrote:
> >I've been thinking on some new pesudo-types like SERIAL.
> >
> >1) LAST_MODIFIED is the timestamp of that last time this row was
> >modified. Easy enough to do currently with triggers.
> >2) TIME_CREATED is the timestamp of when this row was first created with
> >an INSERT. I'm not sure how to do this because it needs to be read
> >only.
>
> MS sql server has a TIMESTAMP field which acts exactly like LAST_MODIFIED
> type you proposed. I find this field very handy when attempting to
> synchronize data. I would welcome such a field type in postgres.
>
There already is something called timestamp, and I thought it was a sql
standard type.
--
Joseph Shraibman
jks(at)selectacast(dot)net
Increase signal to noise ratio. http://www.targabot.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin A. Marques | 2001-02-06 23:07:15 | Re: Re: new type proposal |
| Previous Message | Matt Friedman | 2001-02-06 23:05:24 | Using 7.0.3 - Time to upgrade to 7.1 yet? |