Re: Oracle/PostgreSQL incompatibilities - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Oracle/PostgreSQL incompatibilities
Date
Msg-id 106.1065465284@sss.pgh.pa.us
Whole thread Raw
In response to Oracle/PostgreSQL incompatibilities  (Rainer Klute <rainer.klute@epost.de>)
List pgsql-hackers
Rainer Klute <rainer.klute@epost.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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: db encoding
Next
From: Tom Lane
Date:
Subject: Re: index changing