Jacek,
Ouch! I had forgotten that you wanted to do this. I'm afraid this
makes more than just the alertid proposal unworkable. The whole concept
of having summary information for the object, such as a wavelet
decomposition of its lightcurve or even the mean magnitude, that is
updated as we go along is gone too. Living with this would be very
difficult! What alternatives do we have?
Tim
Jacek Becla wrote:
Kirk, Ani
There is one small complication with keeping the most recent
alertid for each Object: it requires updating existing rows.
It would be nice to have the design of largest tables such that
each row is written one, and kept read-only after that.
Such approach guarantees reproducibility, and make it more
manageable (easier to replicate and distribute).
Changes/updates would be done through versioning, but
I'm not sure it is worth using versioning in this case.
Jacek
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
