= Bill's comments on the SAS 39 views =
[wiki:ippToPspsSAS39BillsNotes back up to ippToPspsSAS39BillsNotes]

!StackObjectView is a join of three tables:     
    !ObjectThin
    !StackObjectThin and
    !StackObjectAttributes

Includes all columns from !ObjectThin except for batchID.
A few (bookkeeping) columns are dropped from !StackObjectThin
From !StackObjectAttributes columns that are duplicates from the thin men are dropped.

Mostly looks fine except for the projectionID skycellId issue that I mentioned in my [wiki:BillsSas39PSPSNotes wiki page].

That is the projectionID and skyCellID in StackObjectView do not match the actual stacks that the detections came from - as given by the xStackMetaIDs.

I suggest change the view to incude the values from !StackObjectThin instead  
and it would be useful to add !StackObjectThin.primaryDetection and !StackObjectThin.bestDetection

At a higher level, given the ambiguity do !ObjectThin projectionID & skycellID make sense?
Perhaps they should be called primaryProjectionID, primarySkyCellID ?

If that change were made to the schema then we could include both in !StackObjectView, but I
don't see what value that would add.

'''Flags'''
I also believe that the infoFlags and infoFlag2 are really necessary and should be included in any stack view to help
distinguish non-detected and otherwise likely garbage objects from things that were detected in a particular filter.\

Now that I'm thinking about it  I would suggest elevating xInfoFlag2&4 (or it's invese) to a column xForcedDetection or xDetction.


----
StackApFlxObjectView Join of ObjectThin and StackApFlx

Has the same projectionID, skycellID issue as StackObjectView. Probably should join with StackObjectThin and pick up those columns and primary and best detection.

----
Actually the rest of the Stack views all have the same issue with projectionID and skycellID, primaryDetection and bestDetection and the flags. I would suggest the same changes.