I have two tables: employees and positions. Tables positions and employees relate by the position nk as a foreign key on employees. Consider position is not a hub
but only an employee attribute normalized to a side table.
You can have a look at the case: bin
.co/2qJdD5cCublu.png" rel="nofollow" target="_blank">https://ibin
"Of courselly", employee splits into a hub
, h_employee, and a satellite
Question: How do I deal with the position description, the attribute? Should I join employee to positions and then load the satellite
as if from a larger table? Or would it be more correct to have a second satellite
, holding a single attribute?
Yet another possibil
ity: Load the position_id as an employee attribute to the satellite
, and then load the key-value id/position to a decoder table (alongside some timestamp.)
What are your opinions, gentlemen? I've looked into the book (Building...) and the item 12.2.3 (page 511) says a decode table can be used, but not what would be a best practice. Like, what might be the largest hurdle over time: Maintain JOINs to load satellites
or to manage a decode table?
Thanks ye all and best regards,