Re: [JDBC] Regarding GSoc Application - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: [JDBC] Regarding GSoc Application
Date
Msg-id CADK3HHLQqYzdyUK0iRSM5CA+msRjZdHYwvSKq4T5QZ0NxKwgZQ@mail.gmail.com
Whole thread Raw
In response to Re: [JDBC] Regarding GSoc Application  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [JDBC] Regarding GSoc Application  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Mon, Apr 9, 2012 at 12:45 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
>
>
> On 04/09/2012 12:14 PM, Dave Cramer wrote:
>>
>>
>> So I'm confused, once they link a file to an FDW can't you just read
>> it with an normal select ?
>>
>> What additional functionality will this provide ?
>>
>
>
>
> I'm confused about what you're confused about. Surely this won't be linking
> files to an FDW, but foreign DBMS tables, in anything you can access via
> JDBC. All you'll need on the postgres side is the relevant JDBC driver, so
> you'd have instant access via standard select queries to anything you can
> get a JDBC driver to talk to. That seems to me something worth having.
>
> I imagine it would look rather like this:
>
>   CREATE FOREIGN DATA WRAPPER foodb HANDLER pljava_jdbc_handler
>   OPTIONS (driver 'jdbc.foodb.org');
>   CREATE SERVER myfoodb FOREIGN DATA WRAPPER foodb OPTIONS(host
>   '1.2.3.4', user 'foouser', password 'foopw');
>   CREATE FOREIGN TABLE footbl (id int, data text) SERVER myfoodb;
>   SELECT * from footbl;
>
Well this is certainly more explanation than we have so far.

Is this the intended use case ?

Dave

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [JDBC] Regarding GSoc Application
Next
From: "Kevin Grittner"
Date:
Subject: Re: [JDBC] Regarding GSoc Application