From: | TJ O'Donnell <tjo(at)acm(dot)org> |
---|---|
To: | "Chad" <chadzakary(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: I see this as the end of BDB in MySQL without a doubt. |
Date: | 2006-02-15 20:34:39 |
Message-ID: | 43F3905F.1080402@acm.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Chad" <chadzakary(at)hotmail(dot)com> wrote:
"What we need now is an open source DB with clean APIs into various
places in the software stack (eg we need a Berkeley DB kind of API
under the hood into something like Postgres) A full bells and whistles
relational DB with these low level ACCESS APIs will be a powerfull
thing in the future. PostgreSQL take note. If you don't already have it
you should begin exposing such a thing today in my humble opinion."
I am quite happy with the c-language API for postgres, as far as it's
capabilities and access to low-level postgres. OK, the docs and examples could
be better. Am I missing something in Chad's comments/warnings or is he
missing something in not understanding pg better?
Chad, could you say more about what in the BDB/API is missing and needed in postgres?
Could it be that Oracle's recent company purchases were intended simply to confuse
people about the future of MySQL and therefore ecourage them to select Oracle?
TJ O'Donnell
http://www.gnova.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2006-02-15 20:35:35 | Re: Postgres using 100% CPU |
Previous Message | Magnus Hagander | 2006-02-15 20:30:15 | Re: Postgres using 100% CPU |