Datetime type dropped from v7.3 ?
Steve Howe <howe@carcass.dhs.org> writes:
Just wondering if the datetime type was dropped on purpose from
PostgreSQL 7.3 ?
Yes. Ad-hoc name translations in the parser create bogosities with
respect to schemas --- I forget the details, but it was either drop
"datetime" or make it a reserved keyword. Since datetime has been
deprecated for a couple releases now, the choice seemed clear.
regards, tom lane
Import Notes
Reply to msg id not found: 187125525405.20021107020951@carcass.dhs.orgReference msg id not found: 20021107020851.D78AA744064@relay1.pgsql.comReference msg id not found: 187125525405.20021107020951@carcass.dhs.org
Hello all,
Just wondering if the datetime type was dropped on purpose from
PostgreSQL 7.3 ?
This is not an issue of course, I'll be using timestamp, but it's
weird having that dropped.
-------------------------------
-- On PostgreSQL 7.2:
-------------------------------
howe=# select version();
version
-----------------------------------------------------------------------
PostgreSQL 7.2.1 on i386-portbld-freebsd4.6.2, compiled by GCC 2.95.3
(1 row)
howe=# create table a(b datetime);
CREATE
howe=# \d a
Table "a"
Column | Type | Modifiers
--------+-----------------------------+-----------
b | timestamp without time zone |
-------------------------------
-- On PostgreSQL 7.3:
-------------------------------
howe=# select version ();
version
---------------------------------------------------------------------
PostgreSQL 7.3b3 on i386-unknown-freebsd4.4, compiled by GCC 2.95.3
(1 row)
howe=# create table a(b datetime);
ERROR: Type "datetime" does not exist
-------------
Best regards,
Steve Howe mailto:howe@carcass.dhs.org
Import Notes
Reply to msg id not found: 20021107020851.D78AA744064@relay1.pgsql.comReference msg id not found: 20021107020851.D78AA744064@relay1.pgsql.com
Hello Tom,
Thursday, November 7, 2002, 1:17:00 AM, you wrote:
TL> Steve Howe <howe@carcass.dhs.org> writes:
Just wondering if the datetime type was dropped on purpose from
PostgreSQL 7.3 ?
TL> Yes. Ad-hoc name translations in the parser create bogosities with
TL> respect to schemas --- I forget the details, but it was either drop
TL> "datetime" or make it a reserved keyword. Since datetime has been
TL> deprecated for a couple releases now, the choice seemed clear.
Oh. ok. I'm glad it was intended.
Thanks :)
-------------
Best regards,
Steve Howe mailto:howe@carcass.dhs.org