veniasilente/veekun_pokedex
1
0
Fork 0
mirror of https://github.com/veekun/pokedex.git synced 2024-08-20 18:16:34 +00:00
Code Issues Projects Releases Wiki Activity
veekun_pokedex/pokedex/data/csv/pokemon_dex_numbers.csv

1163 lines
11 KiB
Text
Raw Normal View History

Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
pokemon_id,generation_id,pokedex_number
1,1,1
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
1,2,226
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
2,1,2
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
2,2,227
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
3,1,3
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
3,2,228
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
4,1,4
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
4,2,229
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
5,1,5
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
5,2,230
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
6,1,6
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
6,2,231
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
7,1,7
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
7,2,232
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
8,1,8
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
8,2,233
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
9,1,9
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
9,2,234
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
10,1,10
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
10,2,24
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
11,1,11
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
11,2,25
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
12,1,12
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
12,2,26
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
13,1,13
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
13,2,27
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
14,1,14
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
14,2,28
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
15,1,15
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
15,2,29
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
16,1,16
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
16,2,10
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
17,1,17
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
17,2,11
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
18,1,18
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
18,2,12
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
19,1,19
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
19,2,17
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
20,1,20
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
20,2,18
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
21,1,21
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
21,2,13
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
22,1,22
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
22,2,14
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
23,1,23
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
23,2,50
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
24,1,24
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
24,2,51
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
25,1,25
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
25,2,22
25,3,156
25,4,104
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
26,1,26
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
26,2,23
26,3,157
26,4,105
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
27,1,27
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
27,2,48
27,3,112
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
28,1,28
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
28,2,49
28,3,113
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
29,1,29
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
29,2,95
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
30,1,30
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
30,2,96
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
31,1,31
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
31,2,97
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
32,1,32
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
32,2,98
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
33,1,33
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
33,2,99
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
34,1,34
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
34,2,100
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
35,1,35
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
35,2,41
35,4,100
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
36,1,36
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
36,2,42
36,4,101
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
37,1,37
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
37,2,125
37,3,153
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
38,1,38
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
38,2,126
38,3,154
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
39,1,39
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
39,2,44
39,3,138
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
40,1,40
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
40,2,45
40,3,139
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
41,1,41
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
41,2,37
41,3,63
41,4,28
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
42,1,42
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
42,2,38
42,3,64
42,4,29
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
43,1,43
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
43,2,83
43,3,88
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
44,1,44
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
44,2,84
44,3,89
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
45,1,45
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
45,2,85
45,3,90
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
46,1,46
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
46,2,70
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
47,1,47
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
47,2,71
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
48,1,48
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
48,2,108
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
49,1,49
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
49,2,109
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
50,1,50
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
50,2,132
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
51,1,51
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
51,2,133
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
52,1,52
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
52,2,136
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
53,1,53
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
53,2,137
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
54,1,54
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
54,2,138
54,3,158
54,4,43
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
55,1,55
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
55,2,139
55,3,159
55,4,44
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
56,1,56
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
56,2,134
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
57,1,57
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
57,2,135
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
58,1,58
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
58,2,127
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
59,1,59
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
59,2,128
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
60,1,60
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
60,2,72
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
61,1,61
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
61,2,73
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
62,1,62
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
62,2,74
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
63,1,63
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
63,2,89
63,3,39
63,4,20
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
64,1,64
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
64,2,90
64,3,40
64,4,21
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
65,1,65
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
65,2,91
65,3,41
65,4,22
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
66,1,66
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
66,2,140
66,3,73
66,4,40
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
67,1,67
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
67,2,141
67,3,74
67,4,41
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
68,1,68
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
68,2,142
68,3,75
68,4,42
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
69,1,69
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
69,2,64
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
70,1,70
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
70,2,65
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
71,1,71
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
71,2,66
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
72,1,72
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
72,2,162
72,3,66
72,4,136
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
73,1,73
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
73,2,163
73,3,67
73,4,137
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
74,1,74
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
74,2,34
74,3,57
74,4,31
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
75,1,75
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
75,2,35
75,3,58
75,4,32
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
76,1,76
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
76,2,36
76,3,59
76,4,33
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
77,1,77
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
77,2,201
77,4,90
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
78,1,78
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
78,2,202
78,4,91
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
79,1,79
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
79,2,80
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
80,1,80
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
80,2,81
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
81,1,81
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
81,2,118
81,3,82
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
81,4,178
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
82,1,82
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
82,2,119
82,3,83
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
82,4,179
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
83,1,83
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
83,2,158
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
84,1,84
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
84,2,199
84,3,92
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
85,1,85
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
85,2,200
85,3,93
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
86,1,86
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
86,2,176
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
87,1,87
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
87,2,177
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
88,1,88
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
88,2,116
88,3,106
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
89,1,89
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
89,2,117
89,3,107
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
90,1,90
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
90,2,169
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
91,1,91
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
91,2,170
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
92,1,92
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
92,2,58
92,4,69
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
93,1,93
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
93,2,59
93,4,70
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
94,1,94
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
94,2,60
94,4,71
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
95,1,95
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
95,2,62
95,4,34
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
96,1,96
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
96,2,87
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
97,1,97
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
97,2,88
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
98,1,98
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
98,2,164
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
99,1,99
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
99,2,165
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
100,1,100
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
100,2,120
100,3,84
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
101,1,101
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
101,2,121
101,3,85
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
102,1,102
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
102,2,104
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
103,1,103
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
103,2,105
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
104,1,104
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
104,2,203
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
105,1,105
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
105,2,204
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
106,1,106
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
106,2,144
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
107,1,107
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
107,2,145
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
108,1,108
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
108,2,178
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
108,4,161
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
109,1,109
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
109,2,114
109,3,108
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
110,1,110
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
110,2,115
110,3,109
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
111,1,111
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
111,2,206
111,3,169
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
111,4,186
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
112,1,112
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
112,2,207
112,3,170
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
112,4,187
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
113,1,113
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
113,2,217
113,4,97
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
114,1,114
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
114,2,179
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
114,4,181
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
115,1,115
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
115,2,205
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
116,1,116
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
116,2,186
116,3,184
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
117,1,117
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
117,2,187
117,3,185
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
118,1,118
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
118,2,78
118,3,50
118,4,78
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
119,1,119
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
119,2,79
119,3,51
119,4,79
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
120,1,120
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
120,2,167
120,3,143
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
121,1,121
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
121,2,168
121,3,144
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
122,1,122
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
122,2,156
122,4,95
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
123,1,123
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
123,2,110
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
123,4,195
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
124,1,124
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
124,2,153
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
125,1,125
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
125,2,155
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
125,4,198
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
126,1,126
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
126,2,151
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
126,4,201
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
127,1,127
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
127,2,112
127,3,167
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
128,1,128
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
128,2,148
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
129,1,129
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
129,2,76
129,3,52
129,4,23
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
130,1,130
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
130,2,77
130,3,53
130,4,24
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
131,1,131
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
131,2,219
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
132,1,132
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
132,2,92
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
133,1,133
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
133,2,180
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
133,4,163
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
134,1,134
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
134,2,181
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
134,4,164
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
135,1,135
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
135,2,182
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
135,4,165
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
136,1,136
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
136,2,183
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
136,4,166
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
137,1,137
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
137,2,215
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
137,4,192
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
138,1,138
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
138,2,220
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
139,1,139
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
139,2,221
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
140,1,140
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
140,2,222
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
141,1,141
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
141,2,223
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
142,1,142
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
142,2,224
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
143,1,143
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
143,2,225
143,4,113
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
144,1,144
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
144,2,235
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
145,1,145
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
145,2,236
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
146,1,146
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
146,2,237
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
147,1,147
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
147,2,241
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
148,1,148
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
148,2,242
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
149,1,149
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
149,2,243
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
150,1,150
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
150,2,249
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
151,1,151
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
151,2,250
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
152,1,152
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
152,2,1
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
153,1,153
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
153,2,2
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
154,1,154
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
154,2,3
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
155,1,155
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
155,2,4
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
156,1,156
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
156,2,5
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
157,1,157
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
157,2,6
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
158,1,158
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
158,2,7
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
159,1,159
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
159,2,8
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
160,1,160
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
160,2,9
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
161,1,161
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
161,2,19
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
162,1,162
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
162,2,20
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
163,1,163
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
163,2,15
163,4,106
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
164,1,164
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
164,2,16
164,4,107
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
165,1,165
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
165,2,30
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
166,1,166
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
166,2,31
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
167,1,167
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
167,2,32
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
168,1,168
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
168,2,33
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
169,1,169
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
169,2,39
169,3,65
169,4,30
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
170,1,170
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
170,2,174
170,3,181
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
171,1,171
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
171,2,175
171,3,182
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
172,1,172
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
172,2,21
172,3,155
172,4,103
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
173,1,173
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
173,2,40
173,4,99
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
174,1,174
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
174,2,43
174,3,137
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
175,1,175
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
175,2,46
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
175,4,173
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
176,1,176
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
176,2,47
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
176,4,174
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
177,1,177
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
177,2,159
177,3,162
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
178,1,178
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
178,2,160
178,3,163
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
179,1,179
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
179,2,53
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
180,1,180
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
180,2,54
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
181,1,181
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
181,2,55
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
182,1,182
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
182,2,86
182,3,91
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
183,1,183
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
183,2,130
183,3,55
183,4,125
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
184,1,184
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
184,2,131
184,3,56
184,4,126
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
185,1,185
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
185,2,106
185,4,93
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
186,1,186
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
186,2,75
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
187,1,187
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
187,2,67
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
188,1,188
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
188,2,68
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
189,1,189
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
189,2,69
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
190,1,190
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
190,2,122
190,4,63
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
191,1,191
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
191,2,102
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
192,1,192
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
192,2,103
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
193,1,193
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
193,2,101
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
193,4,183
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
194,1,194
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
194,2,56
194,4,117
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
195,1,195
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
195,2,57
195,4,118
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
196,1,196
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
196,2,184
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
196,4,167
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
197,1,197
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
197,2,185
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
197,4,168
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
198,1,198
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
198,2,208
198,4,74
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
199,1,199
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
199,2,82
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
200,1,200
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
200,2,214
200,4,72
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
201,1,201
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
201,2,61
201,4,114
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
202,1,202
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
202,2,107
202,3,161
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
203,1,203
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
203,2,147
203,3,164
203,4,121
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
204,1,204
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
204,2,93
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
205,1,205
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
205,2,94
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
206,1,206
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
206,2,52
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
207,1,207
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
207,2,189
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
207,4,153
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
208,1,208
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
208,2,63
208,4,35
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
209,1,209
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
209,2,123
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
210,1,210
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
210,2,124
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
211,1,211
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
211,2,161
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
212,1,212
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
212,2,111
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
212,4,196
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
213,1,213
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
213,2,166
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
214,1,214
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
214,2,113
214,3,168
214,4,62
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
215,1,215
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
215,2,213
215,4,144
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
216,1,216
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
216,2,193
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
217,1,217
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
217,2,194
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
218,1,218
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
218,2,211
218,3,103
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
219,1,219
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
219,2,212
219,3,104
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
220,1,220
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
220,2,191
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
220,4,203
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
221,1,221
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
221,2,192
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
221,4,204
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
222,1,222
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
222,2,171
222,3,180
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
223,1,223
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
223,2,172
223,4,132
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
224,1,224
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
224,2,173
224,4,133
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
225,1,225
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
225,2,190
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
226,1,226
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
226,2,197
226,4,141
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
227,1,227
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
227,2,198
227,3,115
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
228,1,228
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
228,2,209
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
228,4,176
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
229,1,229
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
229,2,210
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
229,4,177
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
230,1,230
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
230,2,188
230,3,186
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
231,1,231
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
231,2,195
231,3,165
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
232,1,232
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
232,2,196
232,3,166
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
233,1,233
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
233,2,216
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
233,4,193
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
234,1,234
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
234,2,129
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
235,1,235
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
235,2,157
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
236,1,236
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
236,2,143
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
237,1,237
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
237,2,146
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
238,1,238
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
238,2,152
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
239,1,239
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
239,2,154
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
239,4,197
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
240,1,240
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
240,2,150
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
240,4,200
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
241,1,241
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
241,2,149
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
242,1,242
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
242,2,218
242,4,98
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
243,1,243
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
243,2,238
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
244,1,244
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
244,2,239
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
245,1,245
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
245,2,240
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
246,1,246
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
246,2,244
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
247,1,247
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
247,2,245
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
248,1,248
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
248,2,246
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
249,1,249
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
249,2,247
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
250,1,250
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
250,2,248
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
251,1,251
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
251,2,251
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
252,1,252
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
252,3,1
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
253,1,253
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
253,3,2
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
254,1,254
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
254,3,3
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
255,1,255
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
255,3,4
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
256,1,256
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
256,3,5
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
257,1,257
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
257,3,6
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
258,1,258
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
258,3,7
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
259,1,259
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
259,3,8
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
260,1,260
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
260,3,9
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
261,1,261
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
261,3,10
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
262,1,262
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
262,3,11
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
263,1,263
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
263,3,12
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
264,1,264
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
264,3,13
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
265,1,265
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
265,3,14
265,4,48
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
266,1,266
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
266,3,15
266,4,49
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
267,1,267
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
267,3,16
267,4,50
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
268,1,268
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
268,3,17
268,4,51
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
269,1,269
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
269,3,18
269,4,52
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
270,1,270
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
270,3,19
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
271,1,271
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
271,3,20
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
272,1,272
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
272,3,21
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
273,1,273
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
273,3,22
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
274,1,274
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
274,3,23
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
275,1,275
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
275,3,24
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
276,1,276
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
276,3,25
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
277,1,277
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
277,3,26
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
278,1,278
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
278,3,27
278,4,119
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
279,1,279
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
279,3,28
279,4,120
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
280,1,280
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
280,3,29
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
280,4,157
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
281,1,281
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
281,3,30
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
281,4,158
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
282,1,282
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
282,3,31
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
282,4,159
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
283,1,283
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
283,3,32
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
284,1,284
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
284,3,33
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
285,1,285
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
285,3,34
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
286,1,286
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
286,3,35
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
287,1,287
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
287,3,36
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
288,1,288
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
288,3,37
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
289,1,289
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
289,3,38
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
290,1,290
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
290,3,42
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
291,1,291
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
291,3,43
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
292,1,292
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
292,3,44
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
293,1,293
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
293,3,45
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
294,1,294
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
294,3,46
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
295,1,295
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
295,3,47
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
296,1,296
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
296,3,48
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
297,1,297
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
297,3,49
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
298,1,298
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
298,3,54
298,4,124
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
299,1,299
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
299,3,60
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
299,4,155
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
300,1,300
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
300,3,61
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
301,1,301
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
301,3,62
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
302,1,302
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
302,3,68
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
303,1,303
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
303,3,69
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
304,1,304
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
304,3,70
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
305,1,305
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
305,3,71
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
306,1,306
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
306,3,72
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
307,1,307
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
307,3,76
307,4,86
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
308,1,308
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
308,3,77
308,4,87
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
309,1,309
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
309,3,78
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
310,1,310
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
310,3,79
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
311,1,311
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
311,3,80
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
312,1,312
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
312,3,81
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
313,1,313
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
313,3,86
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
314,1,314
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
314,3,87
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
315,1,315
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
315,3,94
315,4,26
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
316,1,316
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
316,3,95
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
317,1,317
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
317,3,96
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
318,1,318
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
318,3,97
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
319,1,319
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
319,3,98
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
320,1,320
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
320,3,99
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
321,1,321
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
321,3,100
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
322,1,322
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
322,3,101
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
323,1,323
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
323,3,102
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
324,1,324
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
324,3,105
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
325,1,325
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
325,3,110
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
326,1,326
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
326,3,111
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
327,1,327
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
327,3,114
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
328,1,328
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
328,3,116
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
329,1,329
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
329,3,117
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
330,1,330
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
330,3,118
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
331,1,331
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
331,3,119
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
332,1,332
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
332,3,120
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
333,1,333
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
333,3,121
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
333,4,171
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
334,1,334
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
334,3,122
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
334,4,172
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
335,1,335
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
335,3,123
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
336,1,336
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
336,3,124
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
337,1,337
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
337,3,125
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
338,1,338
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
338,3,126
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
339,1,339
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
339,3,127
339,4,80
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
340,1,340
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
340,3,128
340,4,81
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
341,1,341
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
341,3,129
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
342,1,342
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
342,3,130
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
343,1,343
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
343,3,131
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
344,1,344
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
344,3,132
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
345,1,345
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
345,3,133
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
346,1,346
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
346,3,134
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
347,1,347
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
347,3,135
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
348,1,348
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
348,3,136
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
349,1,349
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
349,3,140
349,4,138
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
350,1,350
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
350,3,141
350,4,139
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
351,1,351
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
351,3,142
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
352,1,352
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
352,3,145
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
353,1,353
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
353,3,146
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
354,1,354
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
354,3,147
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
355,1,355
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
355,3,148
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
355,4,189
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
356,1,356
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
356,3,149
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
356,4,190
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
357,1,357
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
357,3,150
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
357,4,185
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
358,1,358
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
358,3,151
358,4,83
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
359,1,359
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
359,3,152
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
359,4,209
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
360,1,360
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
360,3,160
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
361,1,361
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
361,3,171
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
361,4,206
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
362,1,362
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
362,3,172
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
362,4,207
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
363,1,363
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
363,3,173
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
364,1,364
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
364,3,174
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
365,1,365
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
365,3,175
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
366,1,366
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
366,3,176
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
367,1,367
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
367,3,177
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
368,1,368
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
368,3,178
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
369,1,369
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
369,3,179
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
370,1,370
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
370,3,183
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
371,1,371
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
371,3,187
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
372,1,372
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
372,3,188
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
373,1,373
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
373,3,189
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
374,1,374
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
374,3,190
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
375,1,375
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
375,3,191
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
376,1,376
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
376,3,192
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
377,1,377
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
377,3,193
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
378,1,378
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
378,3,194
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
379,1,379
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
379,3,195
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
380,1,380
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
380,3,196
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
381,1,381
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
381,3,197
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
382,1,382
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
382,3,198
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
383,1,383
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
383,3,199
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
384,1,384
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
384,3,200
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
385,1,385
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
385,3,201
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
386,1,386
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
386,3,202
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
387,1,387
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
387,4,1
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
388,1,388
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
388,4,2
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
389,1,389
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
389,4,3
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
390,1,390
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
390,4,4
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
391,1,391
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
391,4,5
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
392,1,392
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
392,4,6
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
393,1,393
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
393,4,7
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
394,1,394
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
394,4,8
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
395,1,395
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
395,4,9
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
396,1,396
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
396,4,10
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
397,1,397
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
397,4,11
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
398,1,398
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
398,4,12
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
399,1,399
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
399,4,13
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
400,1,400
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
400,4,14
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
401,1,401
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
401,4,15
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
402,1,402
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
402,4,16
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
403,1,403
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
403,4,17
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
404,1,404
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
404,4,18
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
405,1,405
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
405,4,19
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
406,1,406
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
406,4,25
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
407,1,407
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
407,4,27
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
408,1,408
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
408,4,36
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
409,1,409
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
409,4,37
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
410,1,410
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
410,4,38
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
411,1,411
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
411,4,39
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
412,1,412
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
412,4,45
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
413,1,413
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
413,4,46
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
414,1,414
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
414,4,47
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
415,1,415
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
415,4,53
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
416,1,416
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
416,4,54
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
417,1,417
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
417,4,55
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
418,1,418
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
418,4,56
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
419,1,419
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
419,4,57
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
420,1,420
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
420,4,58
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
421,1,421
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
421,4,59
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
422,1,422
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
422,4,60
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
423,1,423
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
423,4,61
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
424,1,424
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
424,4,64
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
425,1,425
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
425,4,65
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
426,1,426
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
426,4,66
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
427,1,427
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
427,4,67
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
428,1,428
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
428,4,68
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
429,1,429
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
429,4,73
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
430,1,430
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
430,4,75
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
431,1,431
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
431,4,76
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
432,1,432
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
432,4,77
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
433,1,433
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
433,4,82
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
434,1,434
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
434,4,84
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
435,1,435
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
435,4,85
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
436,1,436
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
436,4,88
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
437,1,437
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
437,4,89
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
438,1,438
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
438,4,92
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
439,1,439
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
439,4,94
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
440,1,440
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
440,4,96
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
441,1,441
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
441,4,102
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
442,1,442
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
442,4,108
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
443,1,443
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
443,4,109
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
444,1,444
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
444,4,110
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
445,1,445
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
445,4,111
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
446,1,446
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
446,4,112
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
447,1,447
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
447,4,115
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
448,1,448
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
448,4,116
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
449,1,449
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
449,4,122
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
450,1,450
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
450,4,123
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
451,1,451
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
451,4,127
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
452,1,452
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
452,4,128
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
453,1,453
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
453,4,129
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
454,1,454
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
454,4,130
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
455,1,455
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
455,4,131
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
456,1,456
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
456,4,134
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
457,1,457
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
457,4,135
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
458,1,458
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
458,4,140
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
459,1,459
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
459,4,142
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
460,1,460
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
460,4,143
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
461,1,461
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
461,4,145
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
462,1,462
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
462,4,180
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
463,1,463
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
463,4,162
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
464,1,464
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
464,4,188
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
465,1,465
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
465,4,182
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
466,1,466
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
466,4,199
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
467,1,467
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
467,4,202
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
468,1,468
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
468,4,175
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
469,1,469
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
469,4,184
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
470,1,470
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
470,4,169
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
471,1,471
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
471,4,170
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
472,1,472
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
472,4,154
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
473,1,473
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
473,4,205
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
474,1,474
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
474,4,194
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
475,1,475
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
475,4,160
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
476,1,476
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
476,4,156
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
477,1,477
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
477,4,191
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
478,1,478
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
478,4,208
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
479,1,479
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
479,4,152
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
480,1,480
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
480,4,146
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
481,1,481
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
481,4,147
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
482,1,482
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
482,4,148
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
483,1,483
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
483,4,149
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
484,1,484
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
484,4,150
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
485,1,485
486,1,486
487,1,487
Added Platinum Sinnoh dex numbers. #24
2009-06-27 04:27:35 +00:00
487,4,210
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
488,1,488
489,1,489
490,1,490
Reordered some rows in mapping tables. This does NOT actually change the data at all! These tables were apparently created with no key defined, so the rows were in arbitrary order -- but when I created and populated the tables in MySQL on nyarumaa, the keys were defined correctly, and InnoDB ordered them by key. This is about what should happen anyway and the discrepancy adds clutter when dumping corrections, so I'm just committing the new order.
2009-05-01 13:29:19 +00:00
490,4,151
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
491,1,491
492,1,492
493,1,493
496,3,202
497,3,202
498,3,202
499,4,46
500,4,46
Reference in a new issue Copy permalink