Suggestions are welcome for additional Named Allergens.
Column | Type | Length | Description |
---|---|---|---|
Allergen_ID | Number (Long) |
4
|
Unique ID for each allergen record |
Allergen_Category_ID | Number (Long) |
4
|
ID of the allergen category that this specific allergen is associated with. |
Category_Index | Number (Integer) |
2
|
Ordinal set index number of this specific allergen in it's allergen category. (1-64) |
Name | Text |
25
|
The specific name of this allergen |
Comments_ID | Number (Long) |
4
|
Record ID of any comments regarding the nature of this allergen. (May be NULL) |
Modified | Date/Time |
8
|
Timestamp when this record was last modified. |
Modified_By | Number (Long) |
4
|
Record ID for the food detective that last updated this record |
Created | Date/Time |
8
|
Timestamp when this record was created. |
Created_By | Number (Long) |
4
|
Record ID for the food detective that created this record |
Each record in the Allergens table points to one record in this table. That is a one to many relationship from these records to those records.
The Comments_ID field in this record can point to a record in the Comments table. This can be a one to one relationship between this table and to that table. If the user does not wish to add any comments about the Location, then this ID field will be NULL.
The Modified_By and Created_By fields in these records each point to single records in the Food Detective table. Because a food detective can create multiple entries in the database, this can produce a many to one relationship between these records and the Food Detective records.
Allergens Table,
Allergen_Category Table,
Comments Table,
Food_Detective Table,
Suggested Named Allergens.
Home | Documentation Last updated on 12/12/00