Are you sure you wanted "current_date" (CURRDATE) and not
"current_timestamp"? "current_date" is not entirely synonymous with an
Oracle DATE since it doesn't have a timestamp component.

As for the outer join syntax, I agree, it's not a treat. I was toying
with the idea of writing a standalone parser but for now (like you) I
bit the bullet and converted it to SQL99 syntax. This would make an
excellent 7.3 feature.

mlw wrote:

 > 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.
 >

-- 
01010101010101010101010101010101010101010101010101

Marc P. Lavergne [wk:407-648-6996]
Product Development
richLAVA Corporation

--

"Anyone who slaps a 'this page is best viewed with
Browser X' label on a Web page appears to be
yearning for the bad old days, before the Web,
when you had very little chance of reading a
document written on another computer, another word
processor, or another network."
-Tim Berners-Lee (Technology Review, July 1996)

01010101010101010101010101010101010101010101010101


Mon, 11 Feb 2002 18:19:32 -0500
Marc Lavergne <mlavergn@richlava.com>
[Fwd: Re: Oracle compatibility]