| From: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
|---|---|
| To: | Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, david(at)fetter(dot)org |
| Subject: | Re: IMPORT FOREIGN SCHEMA statement |
| Date: | 2014-05-27 14:04:39 |
| Message-ID: | 53849B77.1060303@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 27/05/14 13:49, Ronan Dunklau wrote:
>> Between this and the type-mapping questions, it seems likely that
>> we're going to need a way for IMPORT FOREIGN SCHEMA to accept
>> user-supplied control options, which would in general be specific
>> to the FDW being used. (Another thing the SQL committee failed to
>> think about.)
>
> So, without extending the syntax too much, we could add options:
>
> IMPORT FOREIGN SCHEMA remote_schema FROM SERVER server_name INTO local_schema
> [ { LIMIT TO | EXCEPT } (table_name [, ...])]
> [ OPTIONS (option_list) ]
>
> This option list could then contain fdw-specific options, including type
> mapping.
This one looks like good option to me.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-05-27 14:23:57 | Re: IMPORT FOREIGN SCHEMA statement |
| Previous Message | Stephen Frost | 2014-05-27 14:00:31 | Re: IMPORT FOREIGN SCHEMA statement |