| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | rapg12(at)gmail(dot)com |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: incorrect data type in function |
| Date: | 2016-05-24 17:35:38 |
| Message-ID: | 5132.1464111338@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
rapg12(at)gmail(dot)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:
Thanks for the suggestion!
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-05-24 18:05:43 | Re: Mention pg_reload_conf() in ALTER SYSTEM page |
| Previous Message | Tsunakawa, Takayuki | 2016-05-24 06:56:05 | Mention pg_reload_conf() in ALTER SYSTEM page |