On Tue, Feb 10, 2015 at 9:47 PM, Peter Eisentraut wrote:
> On 2/9/15 3:12 AM, Jeff Davis wrote:
>> On Sat, 2015-02-07 at 16:08 -0800, Jeff Davis wrote:
>>> I believe Inclusion Constraints will be important for postgres.
>>
>> I forgot to credit Darren Duncan with the name of this feature:
>>
>> ht
On Tue, Feb 10, 2015 at 09:47:22PM -0500, Peter Eisentraut wrote:
> On 2/9/15 3:12 AM, Jeff Davis wrote:
> > On Sat, 2015-02-07 at 16:08 -0800, Jeff Davis wrote:
> >> I believe Inclusion Constraints will be important for postgres.
> >
> > I forgot to credit Darren Duncan with the name of this feat
On 2/9/15 3:12 AM, Jeff Davis wrote:
> On Sat, 2015-02-07 at 16:08 -0800, Jeff Davis wrote:
>> I believe Inclusion Constraints will be important for postgres.
>
> I forgot to credit Darren Duncan with the name of this feature:
>
> http://www.postgresql.org/message-id/4f8bb9b0.5090...@darrenduncan
On Sat, 2015-02-07 at 16:08 -0800, Jeff Davis wrote:
> I believe Inclusion Constraints will be important for postgres.
I forgot to credit Darren Duncan with the name of this feature:
http://www.postgresql.org/message-id/4f8bb9b0.5090...@darrenduncan.net
Regards,
Jeff Davis
--
Sent v
I believe Inclusion Constraints will be important for postgres.
Unfortunately, my time has been scarce lately, so without help it may
miss 9.6 as well. If someone is interested in working on this with me to
deliver a good submission in a couple months, please let me know.
The idea is to make a gen