Обсуждение: PATCH: Ticket#96: Deferrable unique & primary constraints
Hi,
Please find the attached patch for the DEFERRABLE / INITIALLY DEFERRED keywords for the unique and primary key constraints.
--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise Postgres Company
Вложения
On Fri, Apr 23, 2010 at 1:07 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote: > Hi, > Please find the attached patch for the DEFERRABLE / INITIALLY DEFERRED > keywords for the unique and primary key constraints. Hi, These constraints are implemented using triggers it seems. We need to filter them out of the reverse engineered SQL and not include them in the treeview (as we do for Foreign Key triggers). I was expecting to just apply that one too :-( -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company
On Fri, Apr 23, 2010 at 6:43 PM, Dave Page <dave.page@enterprisedb.com> wrote:
Please find the patch for the same.On Fri, Apr 23, 2010 at 1:07 PM, Ashesh VashiHi,
<ashesh.vashi@enterprisedb.com> wrote:
> Hi,
> Please find the attached patch for the DEFERRABLE / INITIALLY DEFERRED
> keywords for the unique and primary key constraints.
These constraints are implemented using triggers it seems. We need to
filter them out of the reverse engineered SQL and not include them in
the treeview (as we do for Foreign Key triggers).
I was expecting to just apply that one too :-(
--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise Postgres Company
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
Вложения
Thanks, patch applied. On Fri, Apr 23, 2010 at 3:09 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote: > > > On Fri, Apr 23, 2010 at 6:43 PM, Dave Page <dave.page@enterprisedb.com> > wrote: >> >> On Fri, Apr 23, 2010 at 1:07 PM, Ashesh Vashi >> <ashesh.vashi@enterprisedb.com> wrote: >> > Hi, >> > Please find the attached patch for the DEFERRABLE / INITIALLY DEFERRED >> > keywords for the unique and primary key constraints. >> >> Hi, >> >> These constraints are implemented using triggers it seems. We need to >> filter them out of the reverse engineered SQL and not include them in >> the treeview (as we do for Foreign Key triggers). >> >> I was expecting to just apply that one too :-( > > Please find the patch for the same. > > -- > Thanks & Regards, > > Ashesh Vashi > EnterpriseDB INDIA: Enterprise Postgres Company > > >> >> -- >> Dave Page >> EnterpriseDB UK: http://www.enterprisedb.com >> The Enterprise Postgres Company > > > > -- > Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-hackers > > -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company