On Wednesday 17 October 2007, Markus Schiltknecht wrote: > I'm not sure why exactly heights haven't been stored in the revisions > table from day one on, but I certainly think it's a good idea.
That was motivated by the fact that heights are only there for optimization reasons. They are caching the topological ordering of all revisions present in the database and thus don't represent first-order information. The heights can be thrown away and regenerated at any time (like rosters). So, we wanted to keep that information separately. - Thomas -- Thomas Moschny <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
