| From: | Rémi Cura <remi(dot)cura(at)gmail(dot)com> |
|---|---|
| To: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com> |
| Cc: | Manuel Gómez <targen(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: forcing a table (parent in inheritance) tor emain empty |
| Date: | 2016-10-11 17:41:28 |
| Message-ID: | CAJvUf_vvgjQpF5ak_THOjACLs2mqmNtVbeWxH1pY9wbUUuTznA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Perfect !
Cheers,
Rémi C
2016-10-11 19:12 GMT+02:00 Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>:
> On 11/10/2016 19:04, Rémi Cura wrote:
> > This solution is very nice.
> > Sadly the check is inherited by the children
> > (I only want the parent to be empty, not the children).
> >
> > It seems the element that are not inherited are
> >
> > * Indexes
> > * Unique constraints
> > * Primary Keys
> > * Foreign keys
> > * Rules and Triggers
> >
>
> you can specify a "NO INHERIT" on the check constraint, that should
> solve your issue.
>
> --
> Julien Rouhaud
> http://dalibo.com - http://dalibo.org
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2016-10-11 18:17:50 | Re: My DB has has 5TB, many operations are very slow (on Google Cloud Compute) |
| Previous Message | Julien Rouhaud | 2016-10-11 17:12:34 | Re: forcing a table (parent in inheritance) tor emain empty |