<br><br><div class="gmail_quote">On Wed, May 6, 2009 at 12:49 PM, Zulq Alam <span dir="ltr"><<a href="mailto:me@zulq.net">me@zulq.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
When deserializing Dictionary objects, it looks like they are being rehashed. Where and why is this happening?</blockquote><div><br></div><div>I'm sorry I don't know where, but the why is because a deserialized Dictionary (or Set, or any hashed collection) will, if non-empty, contain newly created/deserialized objects whose identity hashes will differ from those of the serialized ones. Since Object>>#= defaults to #== and Object>>#hash defaults to #identityHash an equality-hashed collection still needs to be rehashed when deserialized since #= hashes can depend on identityHash.</div>
<div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">dict1 := Dictionary new.<br>
1 to: 1000 do: [:e | dict1 at: e put: e].<br>
<br>
rep1 := ReferenceStream streamedRepresentationOf: dict1.<br>
dict2 := ReferenceStream unStream: rep1.<br>
rep2 := ReferenceStream streamedRepresentationOf: dict2.<br>
<br>
dict1 = dict2. " true "<br>
rep1 = rep2. " false "<br>
<br>
dict1 array size. " 2560 "<br>
dict2 array size. " 1334 "<br>
<br>
dict1 rehash.<br>
dict1 array size. " 1334 "<br>
<br>
<br>
I'm using ReferenceStreams to store object graphs in a relational database as a BLOB using Glorp. Glorp determines whether to do an updated by comparing the serialized form of objects with their last state. This causes spurious UPDATEs.<br>
<br>
Any ideas?<br>
<br>
Thanks.<br><font color="#888888">
Zulq.<br>
<br>
<br>
</font></blockquote></div><br>