| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Foreign table permissions and cloning |
| Date: | 2011-04-14 18:40:52 |
| Message-ID: | BANLkTikHf+appuBddwckXcLKOaFYkadLMA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 1, 2011 at 5:13 AM, Thom Brown <thom(at)linux(dot)com> wrote:
> On 1 April 2011 12:57, Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp> wrote:
>> NOT NULL constraint on foreign table is just declaration and can't
>> force data integrity. And I noticed that CREATE FOREIGN TABLE
>> document doesn't mention that serial and bigserial can't be used in
>> foreign table. Please see foreign_table_doc.patch for this fix.
>
> I'd be inclined to generalise it to say that default values can't be
> used on a foreign table, and then say that as a result, serial and
> bigserial can't be used.
+1.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-04-14 18:43:52 | Re: Foreign table permissions and cloning |
| Previous Message | Dimitri Fontaine | 2011-04-14 18:37:47 | Re: WIP: Allow SQL-language functions to reference parameters by parameter name |