anchor.diff:  v0.1, 2020-08-14
   :toc:
   
  +|===
  +| Attribute | Value
  +
  +| Status
  +| DESIGN
  +
  +| Target Version
  +| 1.27
  +
  +| Lead
  +| Dave Watkins
  +|===
  +
  +== Overview
  +
  +This design doc discusses approaches to implementing default / constraining value in Waltz.  The driver
  +behind this enhancement is to ensure data consistency in Waltz.  For example if an app is rated as
  +_'Disinvest'_ then it should have should no individual features rated as _'Invest'_.
   
   == Rating Scheme recap
   
  
positive.code: 
  == Challenges
  
  This section outlines some of the challenges we face in implementing a solution for this feature.
  
  
  * **Constraint Relationship**, how do we tell Waltz that there is a constraining relationship between a
    _measurable rating_ and some other value in Waltz (for example the app's overall _investment rating_) ?
  
negative.code: 
  IMPORTANT: moving investment status will impact batch jobs as inserts/updates will fail unless modified.
  
  ==== Example exporters using pivot functions
  
  Database vendors have differing ways of supporting pivoting
  
  .Postgres example
  [source,sql]
  ----
  select a.name, f.*
  