| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Julien Tachoires <julien(dot)tachoires(at)dalibo(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rowtype column and domain subfield with DEFAULT and NOT NULL constraint |
| Date: | 2014-03-12 23:28:01 |
| Message-ID: | CAB7nPqRyBLcjqiHKDvaRyCsCSDV2m+rynJThaqXvETA-fx5BMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 12, 2014 at 11:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Julien Tachoires <julien(dot)tachoires(at)dalibo(dot)com> writes:
>> A customer has reported us a strange behaviour regarding a rowtype
>> column with a domain subfield:
>
> Rowtypes in general do not support defaults for component fields.
And what about adding a TODO item?
Support default values for component fields of rowtypes
We could as well for the time being improve the documentation to
mention that with some examples. For example with some more content on
the page of INSERT.
Regards,
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Kruse | 2014-03-12 23:36:37 | Re: Patch: Show process IDs of processes holding a lock; show relation and tuple infos of a lock to acquire |
| Previous Message | Michael Paquier | 2014-03-12 23:17:19 | Re: Replication slots and footguns |