<br><br><div class="gmail_quote">On Fri, Jan 23, 2009 at 1:45 PM, Shane Hathaway <span dir="ltr"><<a href="mailto:shane@hathawaymix.org">shane@hathawaymix.org</a>></span> wrote:<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="Ih2E3d">Shane Hathaway wrote:<br>
> Assuming your bad script caused your problem, it is likely that packing<br>
> will still mess up your database, since you still probably have mixed-up<br>
> object_state rows. Don't pack until I've had a chance to look again.<br>
<br>
</div>Here is some more analysis. Now that I understand you accidentally<br>
merged two databases into one by forcing copyTransactionsFrom() to run<br>
when it shouldn't, I looked for the transactions you merged. First I<br>
looked for the OIDs with a confused transaction ID.<br>
<br>
<br>
=> select zoid from current_object where tid != (select max(tid) from<br>
object_state where object_state.zoid = current_object.zoid);<br>
zoid<br>
------<br>
7<br>
10<br>
12<br>
11<br>
9<br>
8<br>
(6 rows)</blockquote><div><br>Wow. All of that with some SQL.<br> <br>Out of curiosity what would be the process if you were using FileStorage to diagnose the same problem? Do the same thing by iterating over the entire storage and filling in some structures and doing the comparison manually? Sounds like it would take a few hours, with SQL -- it seems pretty straightforward.<br>
<br>I'm impressed.<br></div></div><br>The sooner this gets into the mainline of ZODB -- the better.<br><br>