Parent - Child Entity scenario in Qlack-Base application

[stephan-sch]

Currently there is no implementation/sample of a Parent-Child entity relationship. Nor OneToOne neither OneToMany

1. Implement a child entity for Employee (e.g. Address). A OneToMany relationship with a new entity would also be neat.
2. Test if by loading an Employee entry from the DB, fetches also the Lazy defined children/lists. If not, implement a sample methodology to initialize also the lazy defined members.

Note: The entity retrieved from the DB may not have the lazy members initialized. The mapper that converts to DTO maybe does that work. So the question is if those entity members are also accessible when a mapper is not used