From: Tom Lane <tgl@sss.pgh.pa.us>
To: rapg12@gmail.com
cc: pgsql-docs@postgresql.org
Subject: Re: incorrect data type in function
In-reply-to: <20160521140046.22591.24672@wrigleys.postgresql.org>
References: <20160521140046.22591.24672@wrigleys.postgresql.org>
Comments: In-reply-to rapg12@gmail.com
	message dated "Sat, 21 May 2016 14:00:46 -0000"
Date: Tue, 24 May 2016 13:35:38 -0400
Message-ID: <5132.1464111338@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

rapg12@gmail.com writes:
> The data types in the function parameter and the returned type were seems
> typed incorrectly or missed typo ... in ORACLE there is no varchar, but
> there is varchar2

According to what I can find on the web, Oracle treats varchar and
varchar2 as interchangeable type names, but they say they might someday
fix varchar to be spec-compliant about distinguishing null from empty
strings.  (I'll believe that when I see it...)

So our examples are not wrong, but nonetheless this is a good suggestion
because changing them creates an opportunity to talk about the general
porting problem of needing to translate Oracle type names to Postgres.
I've pushed a patch based on that:

http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=23f11dc21b0135702a2852aac927bdc4f9d69cef

Thanks for the suggestion!

			regards, tom lane


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs