Re: Schema provider/CA lookup status

Jean Jordaan wrote:


> AFAIR the cache misses we saw were legit. If the schema changes, it isn't found
> in the cache. So the __dict__ is stable and thorough. It's just slooooooooow,
> because it uses all the field objects on the schema, and all the properties of
> each field.

Okay, so it's calculating the hash key that makes it slow. That makes sense.

I just don't quite know how we'd invalidate the cache. I suppose we 
could define some event that we'd expect people to fire when they 
changed the schema...

Martin


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV