Prev: Building a string out of table columns values
Next: A new approach to learning from Knowledge Horizon
From: --CELKO-- on 30 Mar 2010 17:06
without any specs or DDL, it looks like you have a split attribute
design error. Are "fixed" and "non-fixed" attributes of a work-space
or are they really separate entities? You posted another question
about using COALESCE() to combine two tables with a long list of
common attributes, so it is suspect.
A split attribute is having tables like MalePersonnel and
FemalePersonnel instead of Personnel. This leads to writing UNIONs and
tons of COALESCE() expression to build a correct set.