Re: Problem with recent PostgreSQL relatedpressrelease

From: Jim Nasby <decibel(at)decibel(dot)org>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL Advocacy List <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Problem with recent PostgreSQL relatedpressrelease
Date: 2007-07-13 21:02:51
Message-ID: E82218D6-F051-45D2-8136-21AC3014F954@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On Jul 13, 2007, at 3:24 PM, Joshua D. Drake wrote:
> Jonah H. Harris wrote:
>> On 7/13/07, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>>> That kind of makes my point :)
>> The fact is, if you write a PostgreSQL-only app, it will run
>> perfectly
>> on PostgreSQL or EnterpriseDB.
>
> But that isn't what I asked. I asked if I wrote an EnterpriseDB app
> would it run on PostgreSQL, the answer is clearly no. Yes, yes we
> can of course not use Enterprise (Oracle) features, but one of the
> benefits of EnterpriseDB is that I "can" use those Oracle features.
>
> That is my only point.

And if someone buys Mammoth and sets up replication, they're just as
locked-in. Actually more-so, since EnterpriseDB can be used as a
"bridge" to get you from Oracle to PostgreSQL or vice-versa.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Kris Jurka 2007-07-13 21:04:24 Re: Problem with recent PostgreSQL relatedpressrelease
Previous Message Andreas Pflug 2007-07-13 21:01:31 Re: Problem with recent PostgreSQL relatedpressrelease