Re: SQL/MED compatible connection manager - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: SQL/MED compatible connection manager
Date
Msg-id 36e682920812151230u1f4ca189r1681c29dec2d2e69@mail.gmail.com
Whole thread Raw
In response to Re: SQL/MED compatible connection manager  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: SQL/MED compatible connection manager  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Fri, Dec 12, 2008 at 7:55 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> Now I have a question about the FDW C interface.  The way I understand it,
> an SQL/MED-enabled server and a FDW each have a specific API by which they
> communicate.  Supposedly, each database vendor should be able to ship a
> binary library for its FDW and each SQL/MED-enabled server should be able to
> load and use it.  (If you don't believe in binary compatibility, then I
> think there should at least be source-level interface compatibility.)

Yes, all FDWs should be similar to ODBC drivers in that they are
self-contained and interface with the database through a defined API.
What happens inside them should be irrelevant to PG.

-- 
Jonah H. Harris, Senior DBA
myYearbook.com


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Sync Rep: First Thoughts on Code
Next
From: Peter Eisentraut
Date:
Subject: Re: Function with defval returns error