pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: wieck@debis.com
To: russ@psyex.com
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Oracle sql queries
Date: Wed, 29 Dec 1999 01:46:35 +0100 (MET)
Message-ID: <m1237G7-0003kGC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <v03110707b48ee1e19042@[216.103.219.237]>

> Will any legal Oracle sql syntax work in postgresql?  I'm worried about
> whether tcl scripts that make sql calls to an Oracle db can be used in a
> postgresql without problems.  I guess that brings up two issues:
>
> 1- Is the version of sql that Oracle uses legal in postgres?

Pardon, but...

    is  the  Oracle  SQL  dialect  legal at all? They claim to be
    compliant (to whatever), but after reading the SQL3  specs  I
    think  these Oracle folks have the same (wrong) understanding
    of the words LEGAL and STANDARD as the M$ folks have.  Is  it
    allways  that  people,  who  think  they are a market leader,
    think they can make STANDARD whatever their programmers  hack
    into?

    Legal  is  what the standard defines. The standards are SQL92
    and SQL3.  And AFAIK, Oracle is close to them, but  NOT  100%
    compliant.

    Also,  SQL92  and  SQL3 specs contain many details, where the
    words "implementation defined" appear. So there  is  no  real
    standard at all.

    To answer ur question: No, not ANY Oracle syntax will execute
    the same in PostgreSQL. Especially  things  like  DB  schema,
    stored  procedures, functions and triggers will cause porting
    efford. PostgreSQL is somewhat SQL92 compliant, a little  bit
    SQL3  compliant,  and  somewhere proprietary (as all SQL DB's
    are today). But it's definitely NOT a plug'n'play replacement
    for any commercial database.

    Decide  on  ur  own,  if you wanna spend the next license fee
    into some porting efford and give it a try. If you fail, it's
    a  limited  risk,  if  you  succeed, run free of charge until
    infinity.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #





view thread (3+ messages)

Message-ID: <m1237G7-0003kGC@orion.SAPserv.Hamburg.dsh.de>
Permalink:  ../m1237G7-0003kGC@orion.SAPserv.Hamburg.dsh.de/
Also on:    postgresql.org/message-id/m1237G7-0003kGC@orion.SAPserv.Hamburg.dsh.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: wieck@debis.com, russ@psyex.com
  Subject: Re: [SQL] Oracle sql queries
  In-Reply-To: <m1237G7-0003kGC@orion.SAPserv.Hamburg.dsh.de>
  References: <v03110707b48ee1e19042@[216.103.219.237]> <m1237G7-0003kGC@orion.SAPserv.Hamburg.dsh.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox