Re: Oracle/PostgreSQL incompatibilities

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: rainer(dot)klute(at)epost(dot)de
Cc: klute(at)rainer-klute(dot)de, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Oracle/PostgreSQL incompatibilities
Date: 2003-10-06 18:34:44
Message-ID: 106.1065465284@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rainer Klute <rainer(dot)klute(at)epost(dot)de> writes:
> Here's an Oracle example:

> create table BUSINESS_PROCESS
> (ID NUMBER not null primary key,
> BUSINESS_PROTOCOL varchar2(254),
> PROTOCOL_VERSION varchar2(254),
> DEFAULT_CONVERSATION_TIMEOUT NUMBER);

Oh, just another nonstandard datatype name then. You could use CREATE
DOMAIN to create NUMBER as an alias for integer (or bigint or numeric,
depending on what range of values you're expecting).

varchar2 is harder since we don't have any provision for precision
options on domains. You'll pretty much have to search-and-replace
that to varchar in your schema file :-(

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-10-06 18:37:31 Re: index changing
Previous Message Peter Eisentraut 2003-10-06 18:30:47 Re: db encoding