Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Feb 2003 15:52:15 -0600
From:      Mike Meyer <mwm-dated-1046641935.d0c9b7@mired.org>
To:        Trent Nelson <trent@limekiln.vcisp.net>
Cc:        "Philip M. Gollucci" <philip@p6m7g8.com>, synrat <synrat@wirewalk.org>, questions@freebsd.org
Subject:   Re: Oracle on FreeBSD
Message-ID:  <15963.58767.33461.809290@guru.mired.org>
In-Reply-To: <20030225184430.GA73776@limekiln.vcisp.net>
References:  <1046128729.490.8.camel@dethstar> <Pine.LNX.4.50.0302242257420.21216-100000@mail.wirewalk.com> <200302242321.04463.philip@p6m7g8.com> <20030225091453.GB70361@limekiln.vcisp.net> <15963.38404.257921.610622@guru.mired.org> <20030225184430.GA73776@limekiln.vcisp.net>

next in thread | previous in thread | raw e-mail | index | archive | help
In <20030225184430.GA73776@limekiln.vcisp.net>, Trent Nelson <trent@limekiln.vcisp.net> typed:
> On Tue, Feb 25, 2003 at 10:12:52AM -0600, Mike Meyer wrote:
> > In <20030225091453.GB70361@limekiln.vcisp.net>, Trent Nelson <trent@limekiln.vcisp.net> typed:
> > >     I'm interested in seeing how well something like PostgreSQL can be
> > >     used as a ``drop-in'' replacement for Oracle.  If I have clients 
> > >     connecting via ODBC (Rational ClearQuest), I personally couldn't
> > >     care what the underlying database is.  Now *that* is something I'd
> > >     be interested in seeing a write up for.
> > It's not a drop-in replacement. You have to install the PostgreSQL
> > ODBC drivers on all the clients. Any client-side scripts will have to
> > be changed to use a PostgreSQL wrappers instead of Oracle
> > wrappers. The SQL is probably subtly different as well.
> > SQL may be a standard, but you still get locked into the databases
> > that you can query with it.
>     Perhaps I should have been more specific.  I'm interested in how far
>     you can get (i.e. what queries will work, what ones won't) before
>     you reach a complete road-block.

That requires in-depth knowledge of both systems, which I try to avoid
having. I try to write plain-jane SQL so it will work on anything, or
use standardized wrappers that are available for a number of
databases.

>     With regards to ODBC, changing the
>     driver being used by the application's '*odbc.ini' configuration fi-
>     le is sufficient for modifying the database being interfaced to, is
>     it not?  i.e. the application simply calls standard ODBC functions
>     which the individual database drivers implement.

Right. Having to do it on every client means I won't call it a drop-in
replacement. Drop-ins should be transparent to the clients.

	<mike

-- 
Mike Meyer <mwm@mired.org>		http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15963.58767.33461.809290>