Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: gzh <gzhcoder(at)126(dot)com>
Cc: "Erik Wienhold" <ewie(at)ewie(dot)name>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
Date: 2023-04-27 14:11:22
Message-ID: 1109902.1682604682@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

gzh <gzhcoder(at)126(dot)com> writes:
> I did the following two tests and found that the return value of pg_catalog.date and oracle.date are inconsistent.

Yeah ... that's pretty much the point. Oracle uses the name "date"
for a data type that Postgres (and the SQL standard) calls a "timestamp".
That's very ancient on their side and I doubt they'll ever change it.

If you're porting a bunch of code written for Oracle to Postgres,
you'd have to run around and change every occurrence of "date" to
"timestamp" ... unless you install orafce, in which case you can
rely on this alias type that orafce creates. But you do then have
two types named "date" in the system, so you have to be careful
about search_path settings or you'll get more confusion than it's
worth.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Xu 2023-04-27 19:40:12 Postgres query doesn't accept double quote around schema name in query statement
Previous Message Erik Wienhold 2023-04-27 13:20:57 Re: Re:Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist