Received: from gromit.dotclick.com (host178.mydotclick.com [64.2.137.178])
	by postgresql.org (8.11.3/8.11.4) with ESMTP id g1BJnZE03499
	for <pgsql-hackers@postgresql.org>;
	Mon, 11 Feb 2002 14:49:35 -0500 (EST)
	(envelope-from markw@mohawksoft.com)
Received: from mohawksoft.com (IDENT:markw@localhost.localdomain [127.0.0.1])
	by gromit.dotclick.com (8.9.3/8.9.3) with ESMTP id OAA22121
	for <pgsql-hackers@postgresql.org>; Mon, 11 Feb 2002 14:49:10 -0500
Message-ID: <3C682036.F27CC2EF@mohawksoft.com>
Date: Mon, 11 Feb 2002 14:49:10 -0500
From: mlw <markw@mohawksoft.com>
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.4.16-qc i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Oracle compatibility
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200202/398
X-Sequence-Number: 18704

I don't know how hard it would be to do, but I have rewritten some
Oracle code to work on PostgreSQL. While rewriting a couple functions,
and the tedium of changing SYSDATE to CURRDATE were a pain, these things
can be handled with a scripting language. The big problem, which means
that PostgreSQL code does not go back to Oracle, is the "join" syntax.

If there was a way to adopt the Oracle join syntax in addition to the
standard join syntax. It would make a great deal of difference. The
tedium of formatting and variable naming can be done by almost anyone.
The rewriting of complex queries into a completely different logical
syntax, can only be done by a knowledgeable person and a good QA team.