Re: Syntax for converting double to a timestamp - Mailing list pgsql-general

From Ron Johnson
Subject Re: Syntax for converting double to a timestamp
Date
Msg-id 44FDF25E.7090603@cox.net
Whole thread Raw
In response to Re: Syntax for converting double to a timestamp  ("Frank Church" <voipfc@googlemail.com>)
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frank Church wrote:
> On 9/5/06, codeWarrior <gpatnude@hotmail.com> wrote:
>> It's generally considered bad form to use reserved words as column
>> names....
>>
>
> I am aware of that - in this case  the column names are chosen to
> reflect exactly the names of the attributes of the event being
> recorded.

Does the timestamp reflect an insert time, update, widget creation
date, etc, etc, etc?  All these attributes modify TIMESTAMP.

For example, UPDATE_TIMESTAMP, CURRENT_TIMESTAMP,
TRANSACTION_TIMESTAMP, CREATION_TIMESTAMP, etc, etc, etc.

- --
Ron Johnson, Jr.
Jefferson LA  USA

Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE/fJeS9HxQb37XmcRAjpRAJ0V0id/uxVZWE6hC45IZzlJzVKNHgCdEbbN
YoMAOqezJ77VAbEnpUNpF1U=
=jYb6
-----END PGP SIGNATURE-----

pgsql-general by date:

Previous
From: "Frank Church"
Date:
Subject: Re: Syntax for converting double to a timestamp
Next
From: Charlie Savage
Date:
Subject: ERROR: Gin doesn't support full scan due to it's awful inefficiency