On Fri, 03 Oct 2003 11:53:05 -0400 Tom Lane <[EMAIL PROTECTED]> wrote:
> Rainer Klute <[EMAIL PROTECTED]> writes:
> > [ some good comments, but a few things I want to respond to ]
>
> >+ CREATE SCHEMA: Sometimes a schema created in PostgreSQL
> > disappears if there is nothing in it.
>
>
Rainer Klute <[EMAIL PROTECTED]> 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
Finger or brain trouble, here is the correction :
>NUMBER -> INTEGER when transporting schemas from Oracle to Pg.
>(This needs a little care - as NUMBER in Oracle has bigger *precision*
than INTEGER in Pg)
Thinking about this a bit more, its probably fine to just substitute
NUMERIC for NUMBER,
I think he means that you can do this in oracle :
CREATE TABLE test (id NUMBER);
Oracle treats NUMBER as NUMBER(40) I think.
This seems to be an example of Oracle making up standards as they go
along - do we want to copy this sort of thing ?
I usually just run a substitution of NUMBER(..) -> NU
+ CREATE SCHEMA: Sometimes a schema created in PostgreSQL
disappears if there is nothing in it.
This is more than a bit hard to believe. Can you give an example?
We use schema's ALOT in our applications. I have yet to see this happen.
+ PostgreSQL does not support the NUMBER key
Rainer Klute <[EMAIL PROTECTED]> writes:
> [ some good comments, but a few things I want to respond to ]
>+ CREATE SCHEMA: Sometimes a schema created in PostgreSQL
> disappears if there is nothing in it.
This is more than a bit hard to believe. Can you give an example?
>+ CREATE SE
>+ CREATE SCHEMA: Sometimes a schema created in PostgreSQL
> disappears if there is nothing in it.
If true, this would be a bug. Do you have a reproducible test case?
>+ CREATE INDEX: PostgreSQL should allow specifying a namespace
> for the index, even if the namespace is requi
Ladies and Gentemen,
in a database project I ported an Oracle database definition to
PostgreSQL 7.3.2 as an aside. During this process I found a
couple of incompatibilities in the SQL dialects of both DBMS.
I compiled the following list for whatever it might be good for -
for example to transscr
