Re: [HACKERS] Date/time types: big change - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Date/time types: big change
Date
Msg-id Pine.GSO.4.02A.10002161931360.16403-100000@Svala.DoCS.UU.SE
Whole thread Raw
In response to Date/time types: big change  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-hackers
On Wed, 16 Feb 2000, Thomas Lockhart wrote:

> I've just committed changes to "reunify" the date/time types.
> "timestamp" and "interval" are now the two primary date/time types for
> users. Also, I've changed the default date style to "ISO" (not just in
> time for Y2K, but we'll be ready for "Y3K").

I still don't like our Y2038 status. ;)

Anyway, the question I have is what did you do with functions such as
datetimein() or comparison functions and such for the old types? Did you
remove them? What if some, say, user-defined trigger function uses them?

The reason I'm asking is that I would like to see the floating point types
converted to SQL in a similar fashion, but when I rename, say, float4eq to
realeq it might break user applications. Or not? This is all hypothetical
of course.

-- 
Peter Eisentraut                  Sernanders vaeg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Date/time types: big change
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Date/time types: big changeu