Autogenerated indexes being cached?

[Ryan W]

I'm working to tune my indexes. I noticed a lot of unused indexes, so
I removed everything from my index.yaml and then added back one by one
while running the application locally with the "dev_appserver.py --
require_indexes" command. Everything was working good, so I went
ahead and ran the index vacuum for the production site. All was good
there too.

But, now when I run the app locally with the GoogleAppEngineLauncher
app, not using the --require_indexes flag, it keeps adding back some
autogenerated indexes that aren't used. How do I know they aren't
used? Because the app will run without them with the --
require_indexes flag, and because the counts of the "has been used x
times" are not being incremented.

I've tried restarting the app, removing the app altogether from
GoogleAppEngineLauncher, then adding back. It still keeps adding
these indexes though. Is there a cache somewhere that can reset?

[Alexander Kojevnikov]

Try removing the database access history file, then restarting the
development server. The file is called dev_appserver.datastore.history
and located in the tmp directory.

The development server auto-generates the indices based on the history
file, even if you don't run the corresponding queries after cleaning
up index.yaml

Hope this helps.

Cheers,
Alex
---
www.muspy.com

[Ryan W]

That's it! Thanks Alex.

I had a little trouble tracking down the file, wish this were better
documented. For anybody who discovers this later, I found it here

$ sudo find / -name "dev_appserver.datastore.history" -print
/private/var/folders/Mq/Mq6HCC1-F8enD-Rr+rKv2k+++TI/-Tmp-/
dev_appserver.datastore.history


On Jan 8, 3:02 pm, Alexander Kojevnikov <alexan...@kojevnikov.com>
wrote: