mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-13 17:08:09 +02:00
9999f5a10e
on the namespace not the name; pg_ is not a reserved prefix for table names anymore. From Fernando Nasser.
684 lines
27 KiB
Plaintext
684 lines
27 KiB
Plaintext
--
|
|
-- ALTER_TABLE
|
|
-- add attribute
|
|
--
|
|
CREATE TABLE tmp (initial int4);
|
|
ALTER TABLE tmp ADD COLUMN a int4;
|
|
ALTER TABLE tmp ADD COLUMN b name;
|
|
ALTER TABLE tmp ADD COLUMN c text;
|
|
ALTER TABLE tmp ADD COLUMN d float8;
|
|
ALTER TABLE tmp ADD COLUMN e float4;
|
|
ALTER TABLE tmp ADD COLUMN f int2;
|
|
ALTER TABLE tmp ADD COLUMN g polygon;
|
|
ALTER TABLE tmp ADD COLUMN h abstime;
|
|
ALTER TABLE tmp ADD COLUMN i char;
|
|
ALTER TABLE tmp ADD COLUMN j abstime[];
|
|
ALTER TABLE tmp ADD COLUMN k int4;
|
|
ALTER TABLE tmp ADD COLUMN l tid;
|
|
ALTER TABLE tmp ADD COLUMN m xid;
|
|
ALTER TABLE tmp ADD COLUMN n oidvector;
|
|
--ALTER TABLE tmp ADD COLUMN o lock;
|
|
ALTER TABLE tmp ADD COLUMN p smgr;
|
|
ALTER TABLE tmp ADD COLUMN q point;
|
|
ALTER TABLE tmp ADD COLUMN r lseg;
|
|
ALTER TABLE tmp ADD COLUMN s path;
|
|
ALTER TABLE tmp ADD COLUMN t box;
|
|
ALTER TABLE tmp ADD COLUMN u tinterval;
|
|
ALTER TABLE tmp ADD COLUMN v datetime;
|
|
ALTER TABLE tmp ADD COLUMN w timespan;
|
|
ALTER TABLE tmp ADD COLUMN x float8[];
|
|
ALTER TABLE tmp ADD COLUMN y float4[];
|
|
ALTER TABLE tmp ADD COLUMN z int2[];
|
|
INSERT INTO tmp (a, b, c, d, e, f, g, h, i, j, k, l, m, n, p, q, r, s, t, u,
|
|
v, w, x, y, z)
|
|
VALUES (4, 'name', 'text', 4.1, 4.1, 2, '(4.1,4.1,3.1,3.1)',
|
|
'Mon May 1 00:30:30 1995', 'c', '{Mon May 1 00:30:30 1995, Monday Aug 24 14:43:07 1992, epoch}',
|
|
314159, '(1,1)', '512',
|
|
'1 2 3 4 5 6 7 8', 'magnetic disk', '(1.1,1.1)', '(4.1,4.1,3.1,3.1)',
|
|
'(0,2,4.1,4.1,3.1,3.1)', '(4.1,4.1,3.1,3.1)', '["epoch" "infinity"]',
|
|
'epoch', '01:00:10', '{1.0,2.0,3.0,4.0}', '{1.0,2.0,3.0,4.0}', '{1,2,3,4}');
|
|
SELECT * FROM tmp;
|
|
initial | a | b | c | d | e | f | g | h | i | j | k | l | m | n | p | q | r | s | t | u | v | w | x | y | z
|
|
---------+---+------+------+-----+-----+---+-----------------------+------------------------------+---+------------------------------------------------------------------------------------------------+--------+-------+-----+-----------------+---------------+-----------+-----------------------+-----------------------------+---------------------+---------------------------------------------+--------------------------+------------------+-----------+-----------+-----------
|
|
| 4 | name | text | 4.1 | 4.1 | 2 | ((4.1,4.1),(3.1,3.1)) | Mon May 01 00:30:30 1995 PDT | c | {"Mon May 01 00:30:30 1995 PDT","Mon Aug 24 14:43:07 1992 PDT","Wed Dec 31 16:00:00 1969 PST"} | 314159 | (1,1) | 512 | 1 2 3 4 5 6 7 8 | magnetic disk | (1.1,1.1) | [(4.1,4.1),(3.1,3.1)] | ((0,2),(4.1,4.1),(3.1,3.1)) | (4.1,4.1),(3.1,3.1) | ["Wed Dec 31 16:00:00 1969 PST" "infinity"] | Thu Jan 01 00:00:00 1970 | @ 1 hour 10 secs | {1,2,3,4} | {1,2,3,4} | {1,2,3,4}
|
|
(1 row)
|
|
|
|
DROP TABLE tmp;
|
|
-- the wolf bug - schema mods caused inconsistent row descriptors
|
|
CREATE TABLE tmp (
|
|
initial int4
|
|
);
|
|
ALTER TABLE tmp ADD COLUMN a int4;
|
|
ALTER TABLE tmp ADD COLUMN b name;
|
|
ALTER TABLE tmp ADD COLUMN c text;
|
|
ALTER TABLE tmp ADD COLUMN d float8;
|
|
ALTER TABLE tmp ADD COLUMN e float4;
|
|
ALTER TABLE tmp ADD COLUMN f int2;
|
|
ALTER TABLE tmp ADD COLUMN g polygon;
|
|
ALTER TABLE tmp ADD COLUMN h abstime;
|
|
ALTER TABLE tmp ADD COLUMN i char;
|
|
ALTER TABLE tmp ADD COLUMN j abstime[];
|
|
ALTER TABLE tmp ADD COLUMN k int4;
|
|
ALTER TABLE tmp ADD COLUMN l tid;
|
|
ALTER TABLE tmp ADD COLUMN m xid;
|
|
ALTER TABLE tmp ADD COLUMN n oidvector;
|
|
--ALTER TABLE tmp ADD COLUMN o lock;
|
|
ALTER TABLE tmp ADD COLUMN p smgr;
|
|
ALTER TABLE tmp ADD COLUMN q point;
|
|
ALTER TABLE tmp ADD COLUMN r lseg;
|
|
ALTER TABLE tmp ADD COLUMN s path;
|
|
ALTER TABLE tmp ADD COLUMN t box;
|
|
ALTER TABLE tmp ADD COLUMN u tinterval;
|
|
ALTER TABLE tmp ADD COLUMN v datetime;
|
|
ALTER TABLE tmp ADD COLUMN w timespan;
|
|
ALTER TABLE tmp ADD COLUMN x float8[];
|
|
ALTER TABLE tmp ADD COLUMN y float4[];
|
|
ALTER TABLE tmp ADD COLUMN z int2[];
|
|
INSERT INTO tmp (a, b, c, d, e, f, g, h, i, j, k, l, m, n, p, q, r, s, t, u,
|
|
v, w, x, y, z)
|
|
VALUES (4, 'name', 'text', 4.1, 4.1, 2, '(4.1,4.1,3.1,3.1)',
|
|
'Mon May 1 00:30:30 1995', 'c', '{Mon May 1 00:30:30 1995, Monday Aug 24 14:43:07 1992, epoch}',
|
|
314159, '(1,1)', '512',
|
|
'1 2 3 4 5 6 7 8', 'magnetic disk', '(1.1,1.1)', '(4.1,4.1,3.1,3.1)',
|
|
'(0,2,4.1,4.1,3.1,3.1)', '(4.1,4.1,3.1,3.1)', '["epoch" "infinity"]',
|
|
'epoch', '01:00:10', '{1.0,2.0,3.0,4.0}', '{1.0,2.0,3.0,4.0}', '{1,2,3,4}');
|
|
SELECT * FROM tmp;
|
|
initial | a | b | c | d | e | f | g | h | i | j | k | l | m | n | p | q | r | s | t | u | v | w | x | y | z
|
|
---------+---+------+------+-----+-----+---+-----------------------+------------------------------+---+------------------------------------------------------------------------------------------------+--------+-------+-----+-----------------+---------------+-----------+-----------------------+-----------------------------+---------------------+---------------------------------------------+--------------------------+------------------+-----------+-----------+-----------
|
|
| 4 | name | text | 4.1 | 4.1 | 2 | ((4.1,4.1),(3.1,3.1)) | Mon May 01 00:30:30 1995 PDT | c | {"Mon May 01 00:30:30 1995 PDT","Mon Aug 24 14:43:07 1992 PDT","Wed Dec 31 16:00:00 1969 PST"} | 314159 | (1,1) | 512 | 1 2 3 4 5 6 7 8 | magnetic disk | (1.1,1.1) | [(4.1,4.1),(3.1,3.1)] | ((0,2),(4.1,4.1),(3.1,3.1)) | (4.1,4.1),(3.1,3.1) | ["Wed Dec 31 16:00:00 1969 PST" "infinity"] | Thu Jan 01 00:00:00 1970 | @ 1 hour 10 secs | {1,2,3,4} | {1,2,3,4} | {1,2,3,4}
|
|
(1 row)
|
|
|
|
DROP TABLE tmp;
|
|
--
|
|
-- rename -
|
|
-- should preserve indices, which we can check by seeing if a SELECT
|
|
-- chooses an indexscan; however, in the absence of vacuum statistics
|
|
-- it might not. Therefore, vacuum first.
|
|
--
|
|
VACUUM ANALYZE tenk1;
|
|
ALTER TABLE tenk1 RENAME TO ten_k;
|
|
-- 20 values, sorted
|
|
SELECT unique1 FROM ten_k WHERE unique1 < 20;
|
|
unique1
|
|
---------
|
|
0
|
|
1
|
|
2
|
|
3
|
|
4
|
|
5
|
|
6
|
|
7
|
|
8
|
|
9
|
|
10
|
|
11
|
|
12
|
|
13
|
|
14
|
|
15
|
|
16
|
|
17
|
|
18
|
|
19
|
|
(20 rows)
|
|
|
|
-- 20 values, sorted
|
|
SELECT unique2 FROM ten_k WHERE unique2 < 20;
|
|
unique2
|
|
---------
|
|
0
|
|
1
|
|
2
|
|
3
|
|
4
|
|
5
|
|
6
|
|
7
|
|
8
|
|
9
|
|
10
|
|
11
|
|
12
|
|
13
|
|
14
|
|
15
|
|
16
|
|
17
|
|
18
|
|
19
|
|
(20 rows)
|
|
|
|
-- 100 values, sorted
|
|
SELECT hundred FROM ten_k WHERE hundred = 50;
|
|
hundred
|
|
---------
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
50
|
|
(100 rows)
|
|
|
|
ALTER TABLE ten_k RENAME TO tenk1;
|
|
-- 5 values, sorted
|
|
SELECT unique1 FROM tenk1 WHERE unique1 < 5;
|
|
unique1
|
|
---------
|
|
0
|
|
1
|
|
2
|
|
3
|
|
4
|
|
(5 rows)
|
|
|
|
-- ALTER TABLE ... RENAME on non-table relations
|
|
-- renaming indexes (FIXME: this should probably test the index's functionality)
|
|
ALTER TABLE onek_unique1 RENAME TO tmp_onek_unique1;
|
|
ALTER TABLE tmp_onek_unique1 RENAME TO onek_unique1;
|
|
-- renaming views
|
|
CREATE VIEW tmp_view (unique1) AS SELECT unique1 FROM tenk1;
|
|
ALTER TABLE tmp_view RENAME TO tmp_view_new;
|
|
-- 5 values, sorted
|
|
SELECT unique1 FROM tenk1 WHERE unique1 < 5;
|
|
unique1
|
|
---------
|
|
0
|
|
1
|
|
2
|
|
3
|
|
4
|
|
(5 rows)
|
|
|
|
DROP VIEW tmp_view_new;
|
|
-- renaming sequences
|
|
CREATE SEQUENCE foo_seq;
|
|
ALTER TABLE foo_seq RENAME TO foo_seq_new;
|
|
SELECT * FROM foo_seq_new;
|
|
sequence_name | last_value | increment_by | max_value | min_value | cache_value | log_cnt | is_cycled | is_called
|
|
---------------+------------+--------------+---------------------+-----------+-------------+---------+-----------+-----------
|
|
foo_seq | 1 | 1 | 9223372036854775807 | 1 | 1 | 1 | f | f
|
|
(1 row)
|
|
|
|
DROP SEQUENCE foo_seq_new;
|
|
-- toast-like relation name
|
|
alter table stud_emp rename to pg_toast_stud_emp;
|
|
alter table pg_toast_stud_emp rename to stud_emp;
|
|
-- FOREIGN KEY CONSTRAINT adding TEST
|
|
CREATE TABLE tmp2 (a int primary key);
|
|
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index 'tmp2_pkey' for table 'tmp2'
|
|
CREATE TABLE tmp3 (a int, b int);
|
|
CREATE TABLE tmp4 (a int, b int, unique(a,b));
|
|
NOTICE: CREATE TABLE / UNIQUE will create implicit index 'tmp4_a_key' for table 'tmp4'
|
|
CREATE TABLE tmp5 (a int, b int);
|
|
-- Insert rows into tmp2 (pktable)
|
|
INSERT INTO tmp2 values (1);
|
|
INSERT INTO tmp2 values (2);
|
|
INSERT INTO tmp2 values (3);
|
|
INSERT INTO tmp2 values (4);
|
|
-- Insert rows into tmp3
|
|
INSERT INTO tmp3 values (1,10);
|
|
INSERT INTO tmp3 values (1,20);
|
|
INSERT INTO tmp3 values (5,50);
|
|
-- Try (and fail) to add constraint due to invalid source columns
|
|
ALTER TABLE tmp3 add constraint tmpconstr foreign key(c) references tmp2 match full;
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
ERROR: ALTER TABLE: column "c" referenced in foreign key constraint does not exist
|
|
-- Try (and fail) to add constraint due to invalide destination columns explicitly given
|
|
ALTER TABLE tmp3 add constraint tmpconstr foreign key(a) references tmp2(b) match full;
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
ERROR: UNIQUE constraint matching given keys for referenced table "tmp2" not found
|
|
-- Try (and fail) to add constraint due to invalid data
|
|
ALTER TABLE tmp3 add constraint tmpconstr foreign key (a) references tmp2 match full;
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
ERROR: tmpconstr referential integrity violation - key referenced from tmp3 not found in tmp2
|
|
-- Delete failing row
|
|
DELETE FROM tmp3 where a=5;
|
|
-- Try (and succeed)
|
|
ALTER TABLE tmp3 add constraint tmpconstr foreign key (a) references tmp2 match full;
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
-- Try (and fail) to create constraint from tmp5(a) to tmp4(a) - unique constraint on
|
|
-- tmp4 is a,b
|
|
ALTER TABLE tmp5 add constraint tmpconstr foreign key(a) references tmp4(a) match full;
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
ERROR: UNIQUE constraint matching given keys for referenced table "tmp4" not found
|
|
DROP TABLE tmp5;
|
|
DROP TABLE tmp4;
|
|
DROP TABLE tmp3;
|
|
NOTICE: DROP TABLE implicitly drops referential integrity trigger from table "tmp2"
|
|
NOTICE: DROP TABLE implicitly drops referential integrity trigger from table "tmp2"
|
|
DROP TABLE tmp2;
|
|
-- Foreign key adding test with mixed types
|
|
-- Note: these tables are TEMP to avoid name conflicts when this test
|
|
-- is run in parallel with foreign_key.sql.
|
|
CREATE TEMP TABLE PKTABLE (ptest1 int PRIMARY KEY);
|
|
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index 'pktable_pkey' for table 'pktable'
|
|
CREATE TEMP TABLE FKTABLE (ftest1 inet);
|
|
-- This next should fail, because inet=int does not exist
|
|
ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable;
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
ERROR: Unable to identify an operator '=' for types 'inet' and 'integer'
|
|
You will have to retype this query using an explicit cast
|
|
-- This should also fail for the same reason, but here we
|
|
-- give the column name
|
|
ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable(ptest1);
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
ERROR: Unable to identify an operator '=' for types 'inet' and 'integer'
|
|
You will have to retype this query using an explicit cast
|
|
-- This should succeed, even though they are different types
|
|
-- because varchar=int does exist
|
|
DROP TABLE FKTABLE;
|
|
CREATE TEMP TABLE FKTABLE (ftest1 varchar);
|
|
ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable;
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
-- As should this
|
|
ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable(ptest1);
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
DROP TABLE pktable;
|
|
NOTICE: DROP TABLE implicitly drops referential integrity trigger from table "fktable"
|
|
NOTICE: DROP TABLE implicitly drops referential integrity trigger from table "fktable"
|
|
DROP TABLE fktable;
|
|
CREATE TEMP TABLE PKTABLE (ptest1 int, ptest2 inet,
|
|
PRIMARY KEY(ptest1, ptest2));
|
|
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index 'pktable_pkey' for table 'pktable'
|
|
-- This should fail, because we just chose really odd types
|
|
CREATE TEMP TABLE FKTABLE (ftest1 cidr, ftest2 datetime);
|
|
ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable;
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
ERROR: Unable to identify an operator '=' for types 'cidr' and 'integer'
|
|
You will have to retype this query using an explicit cast
|
|
-- Again, so should this...
|
|
DROP TABLE FKTABLE;
|
|
CREATE TEMP TABLE FKTABLE (ftest1 cidr, ftest2 datetime);
|
|
ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2)
|
|
references pktable(ptest1, ptest2);
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
ERROR: Unable to identify an operator '=' for types 'cidr' and 'integer'
|
|
You will have to retype this query using an explicit cast
|
|
-- This fails because we mixed up the column ordering
|
|
DROP TABLE FKTABLE;
|
|
CREATE TEMP TABLE FKTABLE (ftest1 int, ftest2 inet);
|
|
ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2)
|
|
references pktable(ptest2, ptest1);
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
ERROR: Unable to identify an operator '=' for types 'integer' and 'inet'
|
|
You will have to retype this query using an explicit cast
|
|
-- As does this...
|
|
ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest2, ftest1)
|
|
references pktable(ptest1, ptest2);
|
|
NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
|
|
ERROR: Unable to identify an operator '=' for types 'inet' and 'integer'
|
|
You will have to retype this query using an explicit cast
|
|
-- temp tables should go away by themselves, need not drop them.
|
|
-- test check constraint adding
|
|
create table atacc1 ( test int );
|
|
-- add a check constraint
|
|
alter table atacc1 add constraint atacc_test1 check (test>3);
|
|
-- should fail
|
|
insert into atacc1 (test) values (2);
|
|
ERROR: ExecAppend: rejected due to CHECK constraint atacc_test1
|
|
-- should succeed
|
|
insert into atacc1 (test) values (4);
|
|
drop table atacc1;
|
|
-- let's do one where the check fails when added
|
|
create table atacc1 ( test int );
|
|
-- insert a soon to be failing row
|
|
insert into atacc1 (test) values (2);
|
|
-- add a check constraint (fails)
|
|
alter table atacc1 add constraint atacc_test1 check (test>3);
|
|
ERROR: AlterTableAddConstraint: rejected due to CHECK constraint atacc_test1
|
|
insert into atacc1 (test) values (4);
|
|
drop table atacc1;
|
|
-- let's do one where the check fails because the column doesn't exist
|
|
create table atacc1 ( test int );
|
|
-- add a check constraint (fails)
|
|
alter table atacc1 add constraint atacc_test1 check (test1>3);
|
|
ERROR: Attribute "test1" not found
|
|
drop table atacc1;
|
|
-- something a little more complicated
|
|
create table atacc1 ( test int, test2 int, test3 int);
|
|
-- add a check constraint (fails)
|
|
alter table atacc1 add constraint atacc_test1 check (test+test2<test3*4);
|
|
-- should fail
|
|
insert into atacc1 (test,test2,test3) values (4,4,2);
|
|
ERROR: ExecAppend: rejected due to CHECK constraint atacc_test1
|
|
-- should succeed
|
|
insert into atacc1 (test,test2,test3) values (4,4,5);
|
|
drop table atacc1;
|
|
-- lets do some naming tests
|
|
create table atacc1 (test int check (test>3), test2 int);
|
|
alter table atacc1 add check (test2>test);
|
|
-- should fail for $2
|
|
insert into atacc1 (test2, test) values (3, 4);
|
|
ERROR: ExecAppend: rejected due to CHECK constraint $2
|
|
drop table atacc1;
|
|
-- inheritance related tests
|
|
create table atacc1 (test int);
|
|
create table atacc2 (test2 int);
|
|
create table atacc3 (test3 int) inherits (atacc1, atacc2);
|
|
alter table atacc2 add constraint foo check (test2>0);
|
|
-- fail and then succeed on atacc2
|
|
insert into atacc2 (test2) values (-3);
|
|
ERROR: ExecAppend: rejected due to CHECK constraint foo
|
|
insert into atacc2 (test2) values (3);
|
|
-- fail and then succeed on atacc3
|
|
insert into atacc3 (test2) values (-3);
|
|
ERROR: ExecAppend: rejected due to CHECK constraint foo
|
|
insert into atacc3 (test2) values (3);
|
|
drop table atacc3;
|
|
drop table atacc2;
|
|
drop table atacc1;
|
|
-- let's try only to add only to the parent
|
|
create table atacc1 (test int);
|
|
create table atacc2 (test2 int);
|
|
create table atacc3 (test3 int) inherits (atacc1, atacc2);
|
|
alter table only atacc2 add constraint foo check (test2>0);
|
|
-- fail and then succeed on atacc2
|
|
insert into atacc2 (test2) values (-3);
|
|
ERROR: ExecAppend: rejected due to CHECK constraint foo
|
|
insert into atacc2 (test2) values (3);
|
|
-- both succeed on atacc3
|
|
insert into atacc3 (test2) values (-3);
|
|
insert into atacc3 (test2) values (3);
|
|
drop table atacc3;
|
|
drop table atacc2;
|
|
drop table atacc1;
|
|
-- test unique constraint adding
|
|
create table atacc1 ( test int );
|
|
-- add a unique constraint
|
|
alter table atacc1 add constraint atacc_test1 unique (test);
|
|
NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index 'atacc_test1' for table 'atacc1'
|
|
-- insert first value
|
|
insert into atacc1 (test) values (2);
|
|
-- should fail
|
|
insert into atacc1 (test) values (2);
|
|
ERROR: Cannot insert a duplicate key into unique index atacc_test1
|
|
-- should succeed
|
|
insert into atacc1 (test) values (4);
|
|
-- try adding a unique oid constraint
|
|
alter table atacc1 add constraint atacc_oid1 unique(oid);
|
|
NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index 'atacc_oid1' for table 'atacc1'
|
|
drop table atacc1;
|
|
-- let's do one where the unique constraint fails when added
|
|
create table atacc1 ( test int );
|
|
-- insert soon to be failing rows
|
|
insert into atacc1 (test) values (2);
|
|
insert into atacc1 (test) values (2);
|
|
-- add a unique constraint (fails)
|
|
alter table atacc1 add constraint atacc_test1 unique (test);
|
|
NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index 'atacc_test1' for table 'atacc1'
|
|
ERROR: Cannot create unique index. Table contains non-unique values
|
|
insert into atacc1 (test) values (3);
|
|
drop table atacc1;
|
|
-- let's do one where the unique constraint fails
|
|
-- because the column doesn't exist
|
|
create table atacc1 ( test int );
|
|
-- add a unique constraint (fails)
|
|
alter table atacc1 add constraint atacc_test1 unique (test1);
|
|
ERROR: ALTER TABLE: column "test1" named in key does not exist
|
|
drop table atacc1;
|
|
-- something a little more complicated
|
|
create table atacc1 ( test int, test2 int);
|
|
-- add a unique constraint
|
|
alter table atacc1 add constraint atacc_test1 unique (test, test2);
|
|
NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index 'atacc_test1' for table 'atacc1'
|
|
-- insert initial value
|
|
insert into atacc1 (test,test2) values (4,4);
|
|
-- should fail
|
|
insert into atacc1 (test,test2) values (4,4);
|
|
ERROR: Cannot insert a duplicate key into unique index atacc_test1
|
|
-- should all succeed
|
|
insert into atacc1 (test,test2) values (4,5);
|
|
insert into atacc1 (test,test2) values (5,4);
|
|
insert into atacc1 (test,test2) values (5,5);
|
|
drop table atacc1;
|
|
-- lets do some naming tests
|
|
create table atacc1 (test int, test2 int, unique(test));
|
|
NOTICE: CREATE TABLE / UNIQUE will create implicit index 'atacc1_test_key' for table 'atacc1'
|
|
alter table atacc1 add unique (test2);
|
|
NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index 'atacc1_test2_key' for table 'atacc1'
|
|
-- should fail for @@ second one @@
|
|
insert into atacc1 (test2, test) values (3, 3);
|
|
insert into atacc1 (test2, test) values (2, 3);
|
|
ERROR: Cannot insert a duplicate key into unique index atacc1_test_key
|
|
drop table atacc1;
|
|
-- test primary key constraint adding
|
|
create table atacc1 ( test int );
|
|
-- add a primary key constraint
|
|
alter table atacc1 add constraint atacc_test1 primary key (test);
|
|
ERROR: Existing attribute "test" cannot be a PRIMARY KEY because it is not marked NOT NULL
|
|
-- insert first value
|
|
insert into atacc1 (test) values (2);
|
|
-- should fail
|
|
insert into atacc1 (test) values (2);
|
|
-- should succeed
|
|
insert into atacc1 (test) values (4);
|
|
-- inserting NULL should fail
|
|
insert into atacc1 (test) values(NULL);
|
|
-- try adding a primary key oid constraint
|
|
alter table atacc1 add constraint atacc_oid1 primary key(oid);
|
|
NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index 'atacc_oid1' for table 'atacc1'
|
|
drop table atacc1;
|
|
-- let's do one where the primary key constraint fails when added
|
|
create table atacc1 ( test int );
|
|
-- insert soon to be failing rows
|
|
insert into atacc1 (test) values (2);
|
|
insert into atacc1 (test) values (2);
|
|
-- add a primary key (fails)
|
|
alter table atacc1 add constraint atacc_test1 primary key (test);
|
|
ERROR: Existing attribute "test" cannot be a PRIMARY KEY because it is not marked NOT NULL
|
|
insert into atacc1 (test) values (3);
|
|
drop table atacc1;
|
|
-- let's do another one where the primary key constraint fails when added
|
|
create table atacc1 ( test int );
|
|
-- insert soon to be failing row
|
|
insert into atacc1 (test) values (NULL);
|
|
-- add a primary key (fails)
|
|
alter table atacc1 add constraint atacc_test1 primary key (test);
|
|
ERROR: Existing attribute "test" cannot be a PRIMARY KEY because it is not marked NOT NULL
|
|
insert into atacc1 (test) values (3);
|
|
drop table atacc1;
|
|
-- let's do one where the primary key constraint fails
|
|
-- because the column doesn't exist
|
|
create table atacc1 ( test int );
|
|
-- add a primary key constraint (fails)
|
|
alter table atacc1 add constraint atacc_test1 primary key (test1);
|
|
ERROR: ALTER TABLE: column "test1" named in key does not exist
|
|
drop table atacc1;
|
|
-- something a little more complicated
|
|
create table atacc1 ( test int, test2 int);
|
|
-- add a primary key constraint
|
|
alter table atacc1 add constraint atacc_test1 primary key (test, test2);
|
|
ERROR: Existing attribute "test" cannot be a PRIMARY KEY because it is not marked NOT NULL
|
|
-- try adding a second primary key - should fail
|
|
alter table atacc1 add constraint atacc_test2 primary key (test);
|
|
ERROR: Existing attribute "test" cannot be a PRIMARY KEY because it is not marked NOT NULL
|
|
-- insert initial value
|
|
insert into atacc1 (test,test2) values (4,4);
|
|
-- should fail
|
|
insert into atacc1 (test,test2) values (4,4);
|
|
insert into atacc1 (test,test2) values (NULL,3);
|
|
insert into atacc1 (test,test2) values (3, NULL);
|
|
insert into atacc1 (test,test2) values (NULL,NULL);
|
|
-- should all succeed
|
|
insert into atacc1 (test,test2) values (4,5);
|
|
insert into atacc1 (test,test2) values (5,4);
|
|
insert into atacc1 (test,test2) values (5,5);
|
|
drop table atacc1;
|
|
-- lets do some naming tests
|
|
create table atacc1 (test int, test2 int, primary key(test));
|
|
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index 'atacc1_pkey' for table 'atacc1'
|
|
-- only first should succeed
|
|
insert into atacc1 (test2, test) values (3, 3);
|
|
insert into atacc1 (test2, test) values (2, 3);
|
|
ERROR: Cannot insert a duplicate key into unique index atacc1_pkey
|
|
insert into atacc1 (test2, test) values (1, NULL);
|
|
ERROR: ExecAppend: Fail to add null value in not null attribute test
|
|
drop table atacc1;
|
|
-- alter table / alter column [set/drop] not null tests
|
|
-- try altering system catalogs, should fail
|
|
alter table pg_class alter column relname drop not null;
|
|
ERROR: ALTER TABLE: relation "pg_class" is a system catalog
|
|
alter table pg_class alter relname set not null;
|
|
ERROR: ALTER TABLE: relation "pg_class" is a system catalog
|
|
-- try altering non-existent table, should fail
|
|
alter table foo alter column bar set not null;
|
|
ERROR: Relation "foo" does not exist
|
|
alter table foo alter column bar drop not null;
|
|
ERROR: Relation "foo" does not exist
|
|
-- test setting columns to null and not null and vice versa
|
|
-- test checking for null values and primary key
|
|
create table atacc1 (test int not null);
|
|
alter table atacc1 add constraint "atacc1_pkey" primary key (test);
|
|
NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index 'atacc1_pkey' for table 'atacc1'
|
|
alter table atacc1 alter column test drop not null;
|
|
ERROR: ALTER TABLE: Attribute "test" is in a primary key
|
|
drop index atacc1_pkey;
|
|
alter table atacc1 alter column test drop not null;
|
|
insert into atacc1 values (null);
|
|
alter table atacc1 alter test set not null;
|
|
ERROR: ALTER TABLE: Attribute "test" contains NULL values
|
|
delete from atacc1;
|
|
alter table atacc1 alter test set not null;
|
|
-- try altering a non-existent column, should fail
|
|
alter table atacc1 alter bar set not null;
|
|
ERROR: ALTER TABLE: relation "atacc1" has no column "bar"
|
|
alter table atacc1 alter bar drop not null;
|
|
ERROR: ALTER TABLE: relation "atacc1" has no column "bar"
|
|
-- try altering the oid column, should fail
|
|
alter table atacc1 alter oid set not null;
|
|
ERROR: ALTER TABLE: Cannot alter system attribute "oid"
|
|
alter table atacc1 alter oid drop not null;
|
|
ERROR: ALTER TABLE: Cannot alter system attribute "oid"
|
|
-- try creating a view and altering that, should fail
|
|
create view myview as select * from atacc1;
|
|
alter table myview alter column test drop not null;
|
|
ERROR: ALTER TABLE: relation "myview" is not a table
|
|
alter table myview alter column test set not null;
|
|
ERROR: ALTER TABLE: relation "myview" is not a table
|
|
drop view myview;
|
|
drop table atacc1;
|
|
-- test inheritance
|
|
create table parent (a int);
|
|
create table child (b varchar(255)) inherits (parent);
|
|
alter table parent alter a set not null;
|
|
insert into parent values (NULL);
|
|
ERROR: ExecAppend: Fail to add null value in not null attribute a
|
|
insert into child (a, b) values (NULL, 'foo');
|
|
ERROR: ExecAppend: Fail to add null value in not null attribute a
|
|
alter table parent alter a drop not null;
|
|
insert into parent values (NULL);
|
|
insert into child (a, b) values (NULL, 'foo');
|
|
alter table only parent alter a set not null;
|
|
ERROR: ALTER TABLE: Attribute "a" contains NULL values
|
|
alter table child alter a set not null;
|
|
ERROR: ALTER TABLE: Attribute "a" contains NULL values
|
|
delete from parent;
|
|
alter table only parent alter a set not null;
|
|
insert into parent values (NULL);
|
|
ERROR: ExecAppend: Fail to add null value in not null attribute a
|
|
alter table child alter a set not null;
|
|
insert into child (a, b) values (NULL, 'foo');
|
|
ERROR: ExecAppend: Fail to add null value in not null attribute a
|
|
delete from child;
|
|
alter table child alter a set not null;
|
|
insert into child (a, b) values (NULL, 'foo');
|
|
ERROR: ExecAppend: Fail to add null value in not null attribute a
|
|
drop table child;
|
|
drop table parent;
|