I think I have a simple solution. I haven't looked at all of the places that *PersistKey is used, but it appears that we can simply make persistKey a PersistValue, and get rid of the toPersistKey and fromPersistKey functions. <div>
<br></div><div>I am only half-way through my coffee this morning, but it seems like this could solve all of our problems. Am I off in left field here?<div><br></div><div><br><br><div class="gmail_quote">On Sat, Apr 2, 2011 at 6:57 PM, Rick Richardson <span dir="ltr"><<a href="mailto:rick.richardson@gmail.com">rick.richardson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I ran into another snag getting the tests running for MongoDB backend. The PersistEntity class, and, it appears, the TH is hardcoded to set the key type as Int64. <div>
<br>
<div>This is a problem since the key type in MongoDB is a 12 byte blob. </div><div><br></div></div><div>The other problem is that it looks like PersistBackends are pretty much hardcoded to that type as well. I guess the correct approach would be to allow the designation in mkPersist and then ensure that the PersistBackends can parametrically deal with differing Key types. Or, in the case of MongoDB, hardcode it to a 12 byte blob, because other key types (ObjectId's) rarely make sense. </div>
<div><br></div><div><br></div><div>Thoughts? <br><br><br></div>
</blockquote></div><br></div></div>