The DEFECTTICKET table links the DEFECT table to the TICKET table. Usually, a ticket is created when a suspected issue arises with a product or service. Then, when the issue is investigated, and found that there is an actual problem, a defect is created using the ticket information.
|
If an index entry appears in multiple table columns, then it is a composite index. A composite index requires multiple columns in order to create a unique index. |
Field | Datatype (Length) | Allow Nulls | Indexes | Relationship | Related Table and Field |
---|---|---|---|---|---|
DEFECTTICKETID (PK) |
STANDARDID(12) |
NOT NULL |
DEFECTTICKET_DEFECTTICKETID_PK (CA) |
||
DEFECTID (FK)related to DEFECT.DEFECTID per aa |
STANDARDID(12) |
NOT NULL |
DEFECTTICKET_COMPOSITE (AK) |
(Many) to (One) | |
TICKETID (FK) |
STANDARDID(12) |
NOT NULL |
DEFECTTICKET_COMPOSITE (AK) |
(Many) to (One) |
|
MODIFYDATE |
datetime(8) |
NULLS |
|
|
|
MODIFYUSER (FK) |
char(12) |
NULLS |
|
(Many) to (One) |
|
CREATEDATE |
datetime(8) |
NULLS |
|
|
|
CREATEUSER (FK) |
char(12) |
NULLS |
|
(Many) to (One) |