Table testsql_comments.overduerules
overdue notice status and triggers

 Generated by
SchemaSpy
Legend: SourceForge.net
Primary key columns
Columns with indexes
Excluded column relationships
< n > number of related tables
 
Column Type Size Nulls Auto Default Children Parents Comments
overduerules_id int 10  √ 
overduerules_transport_types
unique identifier for the overduerules
branchcode varchar 10
foreign key from the branches table to define which branch this rule is for (if blank it's all libraries)
categorycode varchar 10
foreign key from the categories table to define which patron category this rule is for
delay1 int 10  √  null number of days after the item is overdue that the first notice is sent
letter1 varchar 20  √  null foreign key from the letter table to define which notice should be sent as the first notice
debarred1 varchar 1  √  0 is the patron restricted when the first notice is sent (1 for yes, 0 for no)
delay2 int 10  √  null number of days after the item is overdue that the second notice is sent
debarred2 varchar 1  √  0 is the patron restricted when the second notice is sent (1 for yes, 0 for no)
letter2 varchar 20  √  null foreign key from the letter table to define which notice should be sent as the second notice
delay3 int 10  √  null number of days after the item is overdue that the third notice is sent
letter3 varchar 20  √  null foreign key from the letter table to define which notice should be sent as the third notice
debarred3 int 10  √  0 is the patron restricted when the third notice is sent (1 for yes, 0 for no)

Table contained 0 rows at Mon Jun 26 10:02 NZST 2017

Indexes:
Column(s) Type Sort
overduerules_id Primary key Asc
branchcode + categorycode Must be unique Asc/Asc

Close relationships  within of separation: