|
|
1.1 root 1: .th QRYMOD ERROR 3/30/79
2: .sh NAME
3: Query Modification error message summary
4: .sh SYNOPSIS
5: Error numbers 3000 \- 3999.
6: .sh DESCRIPTION
7: These error messages are generated by the Query Modification
8: module.
9: These errors include syntactic and semantic problems
10: from view, integrity, and protection definition,
11: as well as run time errors \-
12: such as inability to update a view,
13: or a protection violation.
14: .sh ERRORS
15: .lp +8 8
16: 3310 %0 on view %1: cannot update some domain
17: .s3
18: You tried to perform operation
19: %0 on a view;
20: however, that update is not defined.
21: .s3
22: .lp +8 8
23: 3320 %0 on view %1: domain occurs in qualification of view
24: .s3
25: It is not possible to update a domain in the qualification of
26: a view, since this could cause the tuple to disappear
27: from the view.
28: .s3
29: .lp +8 8
30: 3330 %o on view %1: update would result in more than one query
31: .s3
32: You tried to perform some update
33: on a view
34: which would update two underlying relations.
35: .s3
36: .lp +8 8
37: 3340 %0 on view %1: views do not have TID's
38: .s3
39: You tried to use the Tuple IDentifier field
40: of a view, which is undefined.
41: .s3
42: .lp +8 8
43: 3350 %0 on view %1: cannot update an aggregate value
44: .s3
45: You cannot update a value which is defined in the view
46: definition as an aggregate.
47: .s3
48: .lp +8 8
49: 3360 %0 on view %1: that update might be non-functional
50: .s3
51: There is a chance that the resulting update would be non-functional,
52: that is, that it may have some unexpected side effects.
53: \*(II takes the attitude that it is better
54: to not try the update.
55: .s3
56: .lp +8 8
57: 3490 INTEGRITY on %1: cannot handle aggregates yet
58: .s3
59: You cannot define integrity constraints
60: which include aggregates.
61: .s3
62: .lp +8 8
63: 3491 INTEGRITY on %1: cannot handle multivariable constraints
64: .s3
65: You cannot define integrity constraints
66: on more than a single variable.
67: .s3
68: .lp +8 8
69: 3492 INTEGRITY on %1: constraint does not initially hold
70: .s3
71: When you defined the constraint,
72: there were already tuples in the relation
73: which did not satisfy the constraint.
74: You must fix the relation so that the constraint holds
75: before you can declare the constraint.
76: .s3
77: .lp +8 8
78: 3493 INTEGRITY on %1: is a view
79: .s3
80: You can not define integrity constraints
81: on views.
82: .s3
83: .lp +8 8
84: 3494 INTEGRITY on %1: You must own \*a%1\*a
85: .s3
86: You must own the relation
87: when you declare integrity constraints.
88: .s3
89: .lp +8 8
90: 3500 %0 on relation %1: protection violation
91: .s3
92: You have tried to perform an operation
93: which is not permitted to you.
94: .s3
95: .lp +8 8
96: 3590 PERMIT: bad terminal identifier "%2"
97: .s3
98: In a
99: .it permit
100: statement,
101: the terminal identifier field was improper.
102: .s3
103: .lp +8 8
104: 3591 PERMIT: bad user name "%2"
105: .s3
106: You have used a user name
107: which is not defined on the system.
108: .s3
109: .lp +8 8
110: 3592 PERMIT: Relation \*a%1\*a not owned by you
111: .s3
112: You must own the relation before
113: issuing protection constraints.
114: .s3
115: .lp +8 8
116: 3593 PERMIT: Relation \*a%1\*a must be a real relation (not a view)
117: .s3
118: You can not define permissions on views.
119: .s3
120: .lp +8 8
121: 3594 PERMIT on %1: bad day-of-week \*a%2\*a
122: .s3
123: The day-of-week code was unrecognized.
124: .s3
125: .lp +8 8
126: 3595 PERMIT on %1: only the DBA can use the PERMIT statement
127: .s3
128: Since only the DBA can have shared relations,
129: only the DBA can issue
130: .it permit
131: statements.
132: .s3
133: .lp +8 8
134: 3700 Tree buffer overflow in query modification
135: .lp +8 8
136: 3701 Tree build stack overflow in query modification
137: .s3
138: Bad news.
139: An internal buffer has overflowed.
140: Some expression is too large.
141: Try making your expressions smaller.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.