| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "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 20:20:24 |
| Message-ID: | 36e682920707131320p3935f1a8w6becbf7c77004864@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On 7/13/07, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> That kind of makes my point :)
What point? That using Oracle-proprietary syntax isn't compatible
with PostgreSQL? I don't know anyone who would think that it would
be.
In fact, we have several customers who run EnterpriseDB, but choose
not to utilize the Oracle compatibility features. Which gives them
the option of going to PostgreSQL should they ever want to.
The fact is, if you write a PostgreSQL-only app, it will run perfectly
on PostgreSQL or EnterpriseDB. Like Dave and I said, it's
EnterpriseDB's policy to ensure that PostgreSQL compatibility is fully
maintained.
--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 3rd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2007-07-13 20:23:28 | Re: Problem with recent PostgreSQL relatedpressrelease |
| Previous Message | Joshua D. Drake | 2007-07-13 20:13:45 | Re: Problem with recent PostgreSQL relatedpressrelease |