| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Re[2]: OT ? for people who know other databases besides Orac
Dick,
I've just check on metalink and found notrace of my sql_ansi init.ora parameter :-( but I'm sure there was one (Oracle 7.1 on Novell 3.11).
By the way, I do not know Linda Seley .
Stephane
--- dgoulet_at_vicr.com a écrit : > Stephane,
>
> I'll add your friend onto the addressee list as
> I've had to delve into some
> of her concerns & they are valid.
>
> As far as a init.ora parameter that you
> mentioned I don't remember one in
> any version of Oracle & I've been at this since
> Oracle V3. A check on Metalink
> also came up negative. Now there is a parameter for
> the PRO* precompilers
> called "sqlcheck" which can be set to ansi and a few
> others (full, semantics,
> none, limited).
>
> Now to your friends point, Oracle is using
> PL/SQL & Java (Sun's variant) for
> stored packages, triggers, functions, etc... Other
> RDBMS vendors may either not
> support this functionality or do so via there own
> proprietary methods (I believe
> SQL*Server does it via VB like stuff). Therefore
> there is a definite
> possibility that they may firmly link themselves to
> Oracle as their only
> database vendor or have to maintain separate code
> bases for these types of
> items, one for each db vendor. Not exactly an
> Oracle problem, but I believe
> that's the dark side of "standardization".
>
> Dick Goulet
>
> ____________________Reply
> Separator____________________
> Author: =?iso-8859-1?q?paquette=20stephane?=
> <stephane_paquette_at_yahoo.com>
> Date: 1/31/2001 2:40 AM
>
> On Oracle 7.x there used to be an init.ora parameter
> "sql_ansi" or something that you could set
> true/false
> in order to know if your sql code was ansi
> compatible
> or not.
>
> Unfortunately, this parameter doesn't exist on 8i.
>
> For sure, portability is the opposite of
> performance.
>
> Having your application to work on many rdbms will
> prevent you to have the Oracle only features.
> Or you can build a driver per rdbms in order to used
> each rdbms functionnalities.
>
> Hvae fun !
>
> --- "Seley, Linda" <LSeley_at_IQNavigator.com> a
> écrit :
> > Our Java users are concerned that there may be a
> > possibility that their code
> > may have to work on top of a variety of databases.
>
> > We use Oracle in-house
> > but we, theoretically, may sell our product to
> > another company that uses
> > something else besides Oracle. Our product would
> > then have to talk with
> > their database. What, then, are the advantages
> and
> > disadvantages of using
> > views, procedures, triggers, etc. What would buy
> us
> > the most portability?
> > What headaches might we just have to deal with
> > because there is no way
> > around it?
> >
> > Any insights would be greatly welcomed. Feel free
> > to email me privately at
> > lseley_at_iqnavigator.com.
> >
> > Thanks!
> >
> > Linda
> > --
> > Please see the official ORACLE-L FAQ:
> > http://www.orafaq.com
> > --
> > Author: Seley, Linda
> > INET: LSeley_at_IQNavigator.com
> >
> > Fat City Network Services -- (858) 538-5051
> FAX:
> > (858) 538-5051
> > San Diego, California -- Public Internet
> > access / Mailing Lists
> >
>
 |
 |