Ühel kenal päeval, E, 2006-03-06 kell 17:25, kirjutas Bruce Momjian:
Hannu Krosing wrote:
?hel kenal p?eval, E, 2006-03-06 kell 12:12, kirjutas Bruce Momjian:
Added to TODO:
o Prevent parent tables from altering or dropping constraints
like CHECK that are inherited by
On Wed, 8 Mar 2006, Hannu Krosing wrote:
??hel kenal p??eval, E, 2006-03-06 kell 17:25, kirjutas Bruce Momjian:
Hannu Krosing wrote:
?hel kenal p?eval, E, 2006-03-06 kell 12:12, kirjutas Bruce Momjian:
Added to TODO:
o Prevent parent tables from altering or dropping
Added to TODO:
o Prevent parent tables from altering or dropping constraints
like CHECK that are inherited by child tables
Dropping constraints should only be possible with CASCADE.
and we already have this in TODO:
o %Prevent child tables from altering or
Ühel kenal päeval, E, 2006-03-06 kell 12:12, kirjutas Bruce Momjian:
Added to TODO:
o Prevent parent tables from altering or dropping constraints
like CHECK that are inherited by child tables
Dropping constraints should only be possible with CASCADE.
and we already
Hannu Krosing wrote:
?hel kenal p?eval, E, 2006-03-06 kell 12:12, kirjutas Bruce Momjian:
Added to TODO:
o Prevent parent tables from altering or dropping constraints
like CHECK that are inherited by child tables
Dropping constraints should only be possible
Where are we on this patch? My testing shows it is still shows we have
a problem:
test= CREATE TABLE x(y INT CHECK(y 0));
CREATE TABLE
test= CREATE TABLE z(a INT) inherits (x);
CREATE TABLE
test= ALTER TABLE z DROP CONSTRAINT x_y_check;
On Wed, 2005-12-07 at 21:24 +, Simon Riggs wrote:
Following patch implements record of whether a constraint is inherited
or not, and prevents dropping of inherited constraints.
Patch posted to -patches list.
What it doesn't do:
It doesn't yet prevent dropping the parent constraint, which
Ühel kenal päeval, N, 2005-12-08 kell 11:10, kirjutas Simon Riggs:
On Wed, 2005-12-07 at 21:24 +, Simon Riggs wrote:
Following patch implements record of whether a constraint is inherited
or not, and prevents dropping of inherited constraints.
Patch posted to -patches list.
What it
Another nice (but no doubt more complex) thing would be ability to add
multiple constraints at once, needing only one seqscan to check for
compliance with added constraints and/or making constraint checks
smarter, so that for.ex. ADD CONSTRAINT CHECK i 0 could make use of
index on i instead
On Thu, 2005-12-08 at 11:10 +, Simon Riggs wrote:
On Wed, 2005-12-07 at 21:24 +, Simon Riggs wrote:
Following patch implements record of whether a constraint is inherited
or not, and prevents dropping of inherited constraints.
Patch posted to -patches list.
What it doesn't do:
On Thursday 2005-12-08 15:47, Simon Riggs wrote:
does of course already exist, so the following should cause dependency
violation ERRORs:
- omitting the CASCADE when attempting to delete parent constraint
- attempting to drop the child constraint
Why should dropping the child constraint
11 matches
Mail list logo
