From: gzh <gzhcoder@126.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Erik Wienhold <ewie@ewie.name>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
Date: Tue, 25 Apr 2023 19:34:56 +0800 (CST)
Message-ID: <5027d9b9.7aad.187b831fb18.Coremail.gzhcoder@126.com> (raw)
In-Reply-To: <2993958.1681924695@sss.pgh.pa.us>
References: <328d2a0.828a.18799afd0ac.Coremail.gzhcoder@126.com>
<1597875806.606392.1681915893771@office.mailbox.org>
<70c95d95.7a58.1879a77ed4f.Coremail.gzhcoder@126.com>
<2993958.1681924695@sss.pgh.pa.us>
>The solution is the same whether you upgrade or not: you need
>to adjust your search_path to include the "oracle" schema,
>or else explicitly qualify references to orafce functions.Thank you very much for your help.
To use the to_date functions of Orafce 3.0.1, we created the following to_date function in the public schema of the old database.
-----
CREATE OR REPLACE FUNCTION to_date(str text) RETURNS date AS $$ SELECT $1::date; $$ LANGUAGE sql IMMUTABLE STRICT; COMMENT ON FUNCTION public.to_date(text) IS 'Convert string to date';
-----
To avoid using a to_date function with the same name and parameter in the pg_catalog schema first, the search_path of the old database is set as follows:
"$user", public, pg_catalog
Make sure that public is searched before pg_catalog.
After the database is upgraded, in order to solve the changes in Oracle 3.24, we have added oracle schema to the search_path, as shown below:
"$user", public, oracle, pg_catalog
The following error occurred when I ran my application.
42P13:ERROR:42P13: return type mismatch in function declared to return pg_catalog.date
When I put the oracle schema at the end of the search_path, the problem was solved.
The search_path settings without problems are as follows:
"$user", public, pg_catalog, oracle
Why does it report an error when i put oracle between public and pg_catalog?
At 2023-04-20 01:18:15, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
>gzh <gzhcoder@126.com> writes:
>> Thank you for your prompt reply.
>> Is there another solution if the database is not upgraded to 12.14?
>
>The solution is the same whether you upgrade or not: you need
>to adjust your search_path to include the "oracle" schema,
>or else explicitly qualify references to orafce functions.
>
> regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: gzhcoder@126.com, tgl@sss.pgh.pa.us, ewie@ewie.name
Subject: Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
In-Reply-To: <5027d9b9.7aad.187b831fb18.Coremail.gzhcoder@126.com>
References: <328d2a0.828a.18799afd0ac.Coremail.gzhcoder@126.com> <1597875806.606392.1681915893771@office.mailbox.org> <70c95d95.7a58.1879a77ed4f.Coremail.gzhcoder@126.com> <2993958.1681924695@sss.pgh.pa.us> <5027d9b9.7aad.187b831fb18.Coremail.gzhcoder@126.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox