| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Lorusso Domenico <domenico(dot)l76(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Composite type: Primary Key and validation |
| Date: | 2023-06-05 17:41:59 |
| Message-ID: | CAHyXU0xnK=DrTc4veE3mW=o=vjKmHy_M+=NdxE3t03jk_ub7Xg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jun 5, 2023 at 12:08 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> On Mon, 2023-06-05 at 17:06 +0200, Lorusso Domenico wrote:
> > A composite type is useful because I've to add all these information on
> many tables and because
> > it more easy to pass all these informations to functions that have to
> ensure the right format and evaluation.
> >
> > Talking about first point I could use the "table inheritance", but I've
> to reset all constraints for each table :-(
>
> Inheritance is actually a very good way to do this.
> You don't inherit constraints, but at least the column definitions.
Agreed on not using composite type.
Another suggestion, this might be a good idea for range type.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lorusso Domenico | 2023-06-05 18:19:27 | Re: Composite type: Primary Key and validation |
| Previous Message | Laurenz Albe | 2023-06-05 17:08:15 | Re: Composite type: Primary Key and validation |