[Metakit] Find fails in hashed view but works in plain view or
ordered view.
Thomas Mills Hinkle
tmhinkle at gmail.com
Mon Oct 31 15:13:30 CET 2005
On 10/31/05, Brian Kelley <fustigator at gmail.com> wrote:
> Hashes can be tricky things. Are you sure that you have added all of
> your items to the hashed version and not the underlying view? If you
> create a hash on a view, it must be done before anything is added I
> think.
I'm pretty sure everything was added to the hash -- when the view is
created, I immediately create the hash afterward and then bind my only
reference to it from python to the hashed version.
If this would represent a bug we might be able to track down and fix,
I can try to whip up a quick test-case that reproduces the behavior
and ensures that
> Ordered views have some nicer properties than hash views and I use
> them frequently, a hashed view will start crapping out at around
> 200,000 rows, a blocked and ordered view can be useful with more than
> a million entries.
Ah, good to know. I think I may want to get out of the hashed view
business altogether then.
Tom
More information about the Metakit
mailing list