Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize db again #86

Open
coyotte508 opened this issue Nov 18, 2013 · 1 comment
Open

Optimize db again #86

coyotte508 opened this issue Nov 18, 2013 · 1 comment

Comments

@coyotte508
Copy link
Member

Make all_moves be loaded recursively: Moves from gen 1 are merged to gen 2 moves, and same between gen3, gen4, gen5, gen 6 moves.

So in the python script only add moves for new gens when they aren't in the older gen. Also fix pokemoninfo so that moves between gens are combined. (aka pokemoninfo.moves(poke, 5) will return moves from gen3,4,5 combined, using a .concat probably)

@HRDepartment
Copy link
Contributor

Another necessary optimization is to use default values a bit more often, for example, in pokes/genders.js, many entries have the value 3.

gzip shreds through that kind of data, but it's still not ideal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants