To: John Huttley <john@mwk.co.nz>
Cc: "pgsql-interfaces@postgresql.org" <pgsql-interfaces@postgresql.org>
Subject: Re: Oracle Porting, Compiere 
In-reply-to: <1049172917.12899.30.camel@fileserver.mwk.co.nz> 
References: <1049149006.891.4.camel@fileserver.mwk.co.nz>
	<27772.1049168931@sss.pgh.pa.us>
	<1049172917.12899.30.camel@fileserver.mwk.co.nz>
Comments: In-reply-to John Huttley <john@mwk.co.nz>
	message dated "01 Apr 2003 16:55:17 +1200"
Date: Tue, 01 Apr 2003 00:13:44 -0500
Message-ID: <28385.1049174024@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

John Huttley <john@mwk.co.nz> writes:
> This isn't more that a month or two old.

Okay, it wasn't real clear...

> The previous version worried about nested transactions. 

It still should.  I see no prospect that nested xacts will be in 7.4,
and I wouldn't care to bet they'll be in the release or two after ...

On a more positive note:

* NUMERIC does indeed do the unspecified-precision thing.

* If you can't be bothered to rename datatypes, CREATE DOMAIN would
  serve to provide Oracle-compatible names for Postgres datatypes.
  There is some parse-time overhead associated though.

* CREATE OR REPLACE does exist for some object types now --- views and
  functions for sure, don't recall anything else.

* Postgres *does* do sub-SELECT-in-FROM, which is what I think is meant
  by the references to embedded views.

* On the outer join syntax issue: PG supports the SQL-standard syntax,
  which I believe is also supported by recent Oracle releases.  Consider
  migrating away from Oracle's proprietary syntax.

			regards, tom lane