From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Jean-Michel POURE <jm(at)poure(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Mapping Oracle types to PostgreSQL types |
Date: | 2003-10-17 14:05:16 |
Message-ID: | 22330.1066399516@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Jean-Michel POURE writes:
>> Is there a way to map Oracle nvarchar2(lenght) to PostgreSQL varchar(lenght)
>> in PostgreSQL 7.3? Are there plans to allow such mapping in the future using
>> the CREATE DOMAIN syntax?
> No to both. Doing this would most likely require making the affected type
> names be reserved words in the grammar
Right. At the moment, *all* the type names that support parenthesized
options are hard-wired into the grammar. I think this is probably
unavoidable because otherwise there is a conflict between interpreting
"foo(3)" as a type name and interpreting it as a function call. (But
if anyone can think of a way around that, I'm all ears.)
Since varchar(n) is SQL-standard syntax, can't you simply adopt the more
standard name for both databases?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Conrad | 2003-10-17 14:20:21 | Re: Cisco & Postgres |
Previous Message | Andreas Pflug | 2003-10-17 13:49:44 | Re: Mapping Oracle types to PostgreSQL types |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2003-10-17 14:06:05 | Re: Some thoughts about i/o priorities and throttling vacuum |
Previous Message | Shridhar Daithankar | 2003-10-17 13:55:13 | Re: Some thoughts about i/o priorities and throttling vacuum |