Andrew Ekstedt 3ace3d8aa3 Split pokemon_moves into three tables. ... The idea here is to split each pokemon's moveset into sub-movesets which can be re-used across versions. Thanks to some mapper magic, this should be more or less transparent to users of pokedex. Although i'm sure inserting new moves will be a pain. Before: pokemon_moves: 312,305 rows After: pokemon_movesets: 11,268 rows pokemon_moveset_moves: 123,645 rows pokemon_moveset_version_groups: 23,597 rows total: 158,510 rows		2015-05-25 18:08:42 -07:00
..
__init__.py	General code tidying for this Oracle fix.	2014-02-21 17:48:19 -05:00
dependencies.py	load: Add --recursive option.	2011-04-03 03:17:08 -07:00
load.py	Dump translations for official languages by default.	2014-06-01 19:44:32 -04:00
markdown.py	Only markdownify $target if move.range exists.	2012-08-06 14:10:36 -04:00
multilang.py	"Fix" MultilangQuery.	2015-05-23 18:26:09 -07:00
oracle.py	Update the docstring on rewrite_long_table_names.	2014-02-21 17:59:52 -05:00
tables.py	Split pokemon_moves into three tables.	2015-05-25 18:08:42 -07:00
translations.py	Reading, merging, and writing translations	2011-04-11 17:03:27 +03:00
util.py	Make id lookup util.get use query.get, avoiding queries for dupe lookups	2011-05-06 12:40:44 +03:00