From: | Misa Simic <misa(dot)simic(at)gmail(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com>, Gabriele Bartolini <gabriele(dot)bartolini(at)2ndquadrant(dot)it> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it> |
Subject: | Re: [PATCH] Support for foreign keys with arrays |
Date: | 2012-06-17 11:16:55 |
Message-ID: | -405928980722608358@unknownmsgid |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
IMO, both approaches make sense...
From temporal point no doubt, referencing should be contained by
referenced table....
From other side could be useful if in master table are elements with
simple data type, but for some set of elements there could be common
properties in another table.. What today is doable on the way to in
another table have the same data type and repeat the same properties
for each element...That would be possible with Range data type, though
it does not mean always data are in range so array is probably better
option...
However I am not sure from maintaining point of view, i,e when an
element should be removed from that common properties set - but it is
different topic :)
Kind Regards,
Misa
Sent from my Windows Phone
-----Original Message-----
From: Jeff Davis
Sent: 17/06/2012 08:55
To: Gabriele Bartolini
Cc: PostgreSQL-development; Marco Nenciarini
Subject: Re: [HACKERS] [PATCH] Support for foreign keys with arrays
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2012-06-17 11:37:29 | Re: [patch] libpq one-row-at-a-time API |
Previous Message | Marko Kreen | 2012-06-17 11:14:58 | Re: [patch] libpq one-row-at-a-time API |