Re: ENABLE/DISABLE CONSTRAINT NAME

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: wangshuo(at)highgo(dot)com(dot)cn
Cc: pgsql-hackers(at)postgresql(dot)org, 卢健 <lujian(at)highgo(dot)com(dot)cn>
Subject: Re: ENABLE/DISABLE CONSTRAINT NAME
Date: 2013-09-02 22:42:57
Message-ID: 1378161777.21540.86.camel@jdavis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2013-08-30 at 09:57 +0800, wangshuo(at)highgo(dot)com(dot)cn wrote:
> Hi hackers,
>
> In order to achieve enable/disable constraint name,I made ​​a few
> modifications to the code.
>
> First, someone used to build the constraints while building
> table. Then inserting data must follow a certain order.
> And people usually like to insert the data but not affected by
> foreign keys or check.

Is there any semantic difference between marking a constraint as
DISABLED and simply dropping it? Or does it just make it easier to
re-add it later?

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-09-02 22:52:22 Re: dynamic shared memory
Previous Message Peter Geoghegan 2013-09-02 22:18:42 Re: INSERT...ON DUPLICATE KEY IGNORE