Re: Re: [PATCHES] Select parser at runtime - Mailing list pgsql-hackers

From Vince Vielhaber
Subject Re: Re: [PATCHES] Select parser at runtime
Date
Msg-id Pine.BSF.4.30.0108122211110.82603-100000@paprika.michvhf.com
Whole thread Raw
In response to Re: Re: [PATCHES] Select parser at runtime  (Justin Clift <justin@postgresql.org>)
Responses Re: Re: [PATCHES] Select parser at runtime
Re: Re: [PATCHES] Select parser at runtime
List pgsql-hackers
On Mon, 13 Aug 2001, Justin Clift wrote:

> Hi guys,
>
> Not sure if Peter was joking, but Ian's approach sounds much more
> user-friendly.
>
> Getting Oracle users to convert to PostgreSQL then be "stuck-with-it"
> because they can't afford the migration elsewhere is not the right
> approach.

If you think that people are going to flock to PostgreSQL from Oracle
simply because it's a drop in replacement, I want some of whatever it
is you're drinking!

An Oracle compatibility mode wouldn't be a bad idea, but at what cost
and at how much effort?  What are you going to do with incompatible
reserved words?  Who do you expect to do it?  How soon?  I've seen
alot of projects try to make themselves "user-friendly" only to suffer
in the end from what they lost in the effort.

Personally I'd prefer a PostgreSQL that was as SQL92 and beyond as it
could possibly be rather than some of this and some of that.

Vince.
-- 
==========================================================================
Vince Vielhaber -- KA8CSH    email: vev@michvhf.com    http://www.pop4.net        56K Nationwide Dialup from $16.00/mo
atPop4 Networking       Online Campground Directory    http://www.camping-usa.com      Online Giftshop Superstore
http://www.cloudninegifts.com
==========================================================================





pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [JDBC] JDBC pg_description update needed for CVS tip
Next
From: Tom Lane
Date:
Subject: Re: PL/pgSQL bug?