056 Modeling Composite Lookup Resource Entities for PhbkEmployee

Notes

We say that a Lookup Resource is Composite if it has more than one search property.
We are going to create a lookup resource for three scalar properties:
- EmpLastName
- EmpFirstName
- EmpSecondName
the end user can define a partial filter
- for one prop: EmpLastName
- for two prop: EmpLastName and EmpFirstName
According to the requirements 033 we need to create three lookup dictionary-table and two lookup refs-table. (The number of the lookup refs-tables depends on the number of the foreign keys)
each dictionary table table
- should have two columns:
  - row id column with a primary key on it
  - data column with a unique key on it
  - the name of the data column must be the same as column name of the PhbkEmployee-table
Naming prefix for the lookup dictionary-tables will be Lpd (which means lookup dictionary)
Naming prefix for the lookup refs-tables will be Lpr (which means lookup refs)

Click to show the code