| From: | Tim Uckun <tim(at)diligence(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: new type proposal |
| Date: | 2001-02-06 21:06:22 |
| Message-ID: | 5.0.0.25.2.20010206140423.019f4ad8@mail.diligence.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
BTW is the currency datatype working with access and ODBC yet?
:wq
Tim Uckun
Due Diligence Inc. http://www.diligence.com/ Americas Background
Investigation Expert.
If your company isn't doing background checks, maybe you haven't considered
the risks of a bad hire.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Culley Harrelson | 2001-02-06 21:25:54 | Re: selecting a random record |
| Previous Message | Stefan Waidele jun. | 2001-02-06 20:46:11 | Re: clean rebuild process? |