cvs 6.5 regression tests on Linux x86
6.5 cvs (today), Linux x86 2.2.7, egcs 1.12 release
It seems that int2 and int4 regression tests failed because of
changes in error messages. But I don't know what's going with
triggers test. Does is ok ?
Oleg
diff results/int2.out expected/int2.out
10c10
< ERROR: pg_atoi: error reading "100000": Math result not representable
---
ERROR: pg_atoi: error reading "100000": Numerical result out of range
diff results/int4.out expected/int4.out
10c10
< ERROR: pg_atoi: error reading "1000000000000": Math result not representable
---
ERROR: pg_atoi: error reading "1000000000000": Numerical result out of range
diff results/triggers.out expected/triggers.out
39d38
< ERROR: check_primary_key: even number of arguments should be specified
41d39
< ERROR: check_primary_key: even number of arguments should be specified
43d40
< ERROR: check_primary_key: even number of arguments should be specified
45d41
< ERROR: check_primary_key: even number of arguments should be specified
47c43
< ERROR: check_primary_key: even number of arguments should be specified
---
ERROR: check_fkeys2_pkey_exist: tuple references non-existing key in pkeys
49d44
< ERROR: check_primary_key: even number of arguments should be specified
51d45
< ERROR: check_primary_key: even number of arguments should be specified
53d46
< ERROR: check_primary_key: even number of arguments should be specified
55d47
< ERROR: check_primary_key: even number of arguments should be specified
57c49
< ERROR: check_primary_key: even number of arguments should be specified
---
ERROR: check_fkeys_pkey_exist: tuple references non-existing key in pkeys
59c51
< ERROR: check_primary_key: even number of arguments should be specified
---
ERROR: check_fkeys_pkey2_exist: tuple references non-existing key in fkeys2
61,62c53,54
< NOTICE: check_pkeys_fkey_cascade: 0 tuple(s) of fkeys are deleted
< NOTICE: check_pkeys_fkey_cascade: 0 tuple(s) of fkeys2 are deleted
---
NOTICE: check_pkeys_fkey_cascade: 1 tuple(s) of fkeys are deleted
ERROR: check_fkeys2_fkey_restrict: tuple referenced in fkeys
64,65c56,57
< NOTICE: check_pkeys_fkey_cascade: 0 tuple(s) of fkeys are deleted
< NOTICE: check_pkeys_fkey_cascade: 0 tuple(s) of fkeys2 are deleted
---
NOTICE: check_pkeys_fkey_cascade: 1 tuple(s) of fkeys are deleted
NOTICE: check_pkeys_fkey_cascade: 1 tuple(s) of fkeys2 are deleted
67,68c59,60
< NOTICE: check_pkeys_fkey_cascade: 0 tuple(s) of fkeys are deleted
< NOTICE: check_pkeys_fkey_cascade: 0 tuple(s) of fkeys2 are deleted
---
NOTICE: check_pkeys_fkey_cascade: 1 tuple(s) of fkeys are deleted
ERROR: check_fkeys2_fkey_restrict: tuple referenced in fkeys
70,72c62,63
< NOTICE: check_pkeys_fkey_cascade: 0 tuple(s) of fkeys are deleted
< NOTICE: check_pkeys_fkey_cascade: 0 tuple(s) of fkeys2 are deleted
< ERROR: Cannot insert a duplicate key into a unique index
---
NOTICE: check_pkeys_fkey_cascade: 1 tuple(s) of fkeys are deleted
NOTICE: check_pkeys_fkey_cascade: 1 tuple(s) of fkeys2 are deleted
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
diff results/triggers.out expected/triggers.out 39d38 < ERROR: check_primary_key: even number of arguments should be specified 41d39 < ERROR: check_primary_key: even number of arguments should be specified
Somebody submitted a patch to refint.c, that was only intended as an idea.
I would like to see this patch to check_primary_key(...) reverted, since it:
1. does not give a correct ERROR message (coding error)
2. supplies funktionality, that is rather obscure
(it triggers an insert into a primary table on an insert to a
foreign key table that
would otherwise violate the foreign key constraint)
3. busted the regression test
If you need more info on this issue feel free to ask.
Andreas
Import Notes
Resolved by subject fallback
ZEUGSWETTER Andreas IZ5 <Andreas.Zeugswetter@telecom.at> writes:
ERROR: check_primary_key: even number of arguments should be specified
Somebody submitted a patch to refint.c, that was only intended as an idea.
I would like to see this patch to check_primary_key(...) reverted,
I agree, since no one seems to be willing to take responsibility for
fixing it. Unless someone steps up to bat in the next day or so,
I will take responsibility for backing out the change ;-)
regards, tom lane
Import Notes
Reply to msg id not found: YourmessageofFri7May1999104326+0200219F68D65015D011A8E000006F8590C60267B35E@sdexcsrv1.f000.d0188.sd.spardat.at | Resolved by subject fallback