Return to destroy.nr CVS log

Up to [CSRG BSD Unix] / 43BSD / ingres / doc / quel

Annotation of 43BSD/ingres/doc/quel/destroy.nr, revision 1.1.1.1

1.1       root        1: .th DESTROY QUEL 2/21/79
                      2: .sh NAME
                      3: destroy \- destroy existing relation(s)
                      4: .sh SYNOPSIS
                      5: .bd destroy 
                      6: relname { , relname }
                      7: .br
                      8: .bd destroy 
                      9: [
                     10: .bd permit
                     11: |
                     12: .bd integrity
                     13: ] relname
                     14: [
                     15: integer { , integer }
                     16: |
                     17: .bd all
                     18: ]
                     19: .br
                     20: .bd destroy
                     21: .bd delim
                     22: groupname
                     23: .sh DESCRIPTION
                     24: .it Destroy 
                     25: removes relations from the data base,
                     26: removes constraints or permissions from a relation,
                     27: and removes user-defined delimitors.
                     28: Only the relation owner
                     29: may destroy a relation or its permissions and integrity
                     30: constraints.
                     31: A relation may be emptied of tuples, but not destroyed, using the delete
                     32: statement or the modify statement.
                     33: .s3
                     34: If the relation being destroyed has secondary
                     35: indices on it, the secondary indices are also destroyed.
                     36: Destruction of just a secondary index does not affect the
                     37: primary relation it indexes.
                     38: .s3
                     39: To destroy individual permissions or constraints for a relation,
                     40: the 
                     41: .it integer 
                     42: arguments should be those printed by a 
                     43: .bd "help permit"
                     44: (for 
                     45: .bd destroy 
                     46: .bd permit\c
                     47: )
                     48: or a 
                     49: .bd "help integrity"
                     50: (for 
                     51: .bd destroy
                     52: .bd integrity\c
                     53: ) on the same relation.
                     54: To destroy all constraints or permissions, the 
                     55: .bd all
                     56: keyword may be used in place of individual integers.
                     57: To destroy constraints or permissions, either the
                     58: .it integer
                     59: arguments or the
                     60: .bd all 
                     61: keyword must be present.
                     62: .s3
                     63: To destroy a delimitor group,
                     64: the groupname must be specified.
                     65: This destroys the delimitors permanently,
                     66: as opposed to unusing the group.
                     67: .sh EXAMPLE
                     68: .nf
                     69: /\*(** Destroy the emp relation \*(**/
                     70:     destroy emp
                     71:     destroy emp, parts
                     72: .s1
                     73: /\*(** Destroy some permissions on parts, and all integrity
                     74:  \*(** constraints on employee
                     75:  \*(**/
                     76:    destroy permit parts 0, 4, 5
                     77:    destroy integrity employee
                     78: .s1
                     79: \/* Destroy the "paper" delimitor group \*(**/
                     80:    destroy delim paper
                     81: .fi
                     82: .sh "SEE ALSO"
                     83: create(quel), delete(quel), delim(quel), help(quel), index(quel), modify(quel)

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.