<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 26 May 2009, at 13:47, Chris Browet wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">2009/5/26 Stefan de Konink <span dir="ltr"><<a href="mailto:stefan@konink.de">stefan@konink.de</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="im">Chris Browet wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> If you just want to materialise the entire database at a certain<br> interval, don't you think this will grow very fast?<br> <br> <br> I don't know. A baseline would only consist of a list of all objects id with their associated version number at a certain point in time, not the actual objects...<br> </blockquote> <br></div> Think of a way X; it consist of n nodes. If you take the this way at changeset Y, you would still have to find all nodes positions at time(Y).<br><font color="#888888"> </font></blockquote><div><br>Sure, but as we'd take a version snapshot of all objects anyway, the X way will still be only say 8 bytes for the id and n (don't know the definaition for versions, let's assume 4) bytes for the version. That is 12 bytes per object * 360.000.000 is ~4.5Gb.<br> <br>Assuming daily, one year rotating, online baselines, that makes 1.5 Tb, i.e. 2 big disks (with overhead), i.e. 200€.<br><br>Not that expensive IMHO...<br></div></div></blockquote></div><br><div>I think that you are looking for something that Matt has talked about a few times, and that is a global version number like svn.</div><div><br></div><div>Shaun</div><div><br></div></body></html>