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_egg_groups.csv

911 lines
5.4 KiB
Text
Raw Permalink Normal View History

Pokemon species split: Other data changes
2011-04-29 21:37:14 +00:00
species_id,egg_group_id
Initial commit, with much of the data imported. Includes a wrapper script 'pokedex' that can, so far, read data from a db and spit out CSVs or deploy CSVs to a db.
2009-02-05 08:05:42 +00:00
1,1
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
1,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
2,1
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
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
3,1
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
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
4,1
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
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
5,1
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
5,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
6,1
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
6,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
7,1
7,2
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
8,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
8,2
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
9,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
9,2
10,3
11,3
12,3
13,3
14,3
15,3
16,4
17,4
18,4
19,5
20,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
21,4
22,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
23,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
23,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
24,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
24,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
25,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
25,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
26,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
26,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
27,5
28,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
29,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
29,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
30,15
31,15
32,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
32,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
33,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
33,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
34,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
34,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
35,6
36,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
37,5
38,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
39,6
40,6
41,4
42,4
43,7
44,7
45,7
46,3
46,7
47,3
47,7
48,3
49,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
50,5
51,5
52,5
53,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
54,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
54,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
55,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
55,5
56,5
57,5
58,5
59,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
60,2
61,2
62,2
63,8
64,8
65,8
66,8
67,8
68,8
69,7
70,7
71,7
72,9
73,9
74,10
75,10
76,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
77,5
78,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
79,1
79,2
80,1
80,2
81,10
82,10
83,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
83,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
84,4
85,4
86,2
86,5
87,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
87,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
88,11
89,11
90,9
91,9
92,11
93,11
94,11
95,10
96,8
97,8
98,9
99,9
100,10
101,10
102,7
103,7
104,1
105,1
106,8
107,8
108,1
109,11
110,11
111,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
111,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
112,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
112,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
113,6
114,7
115,1
116,2
116,14
117,2
117,14
118,12
119,12
120,9
121,9
122,8
123,3
124,8
125,8
126,8
127,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
128,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
129,12
129,14
130,12
130,14
131,1
131,2
132,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
133,5
134,5
135,5
136,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
137,10
138,2
138,9
139,2
139,9
140,2
140,9
141,2
141,9
142,4
143,1
144,15
145,15
146,15
147,2
147,14
148,2
148,14
149,2
149,14
150,15
151,15
152,1
152,7
153,1
153,7
154,1
154,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
155,5
156,5
157,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
158,1
158,2
159,1
159,2
160,1
160,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
161,5
162,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
163,4
164,4
165,3
166,3
167,3
168,3
169,4
170,12
171,12
172,15
173,15
174,15
175,15
176,4
176,6
177,4
178,4
179,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
179,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
180,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
180,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
181,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
181,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
182,7
183,2
183,6
184,2
184,6
185,10
186,2
187,6
187,7
188,6
188,7
189,6
189,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
190,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
191,7
192,7
193,3
194,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
194,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
195,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
195,5
196,5
197,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
198,4
199,1
199,2
200,11
201,15
202,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
203,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
204,3
205,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
206,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
207,3
208,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
209,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
209,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
210,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
210,6
211,12
212,3
213,3
214,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
215,5
216,5
217,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
218,11
219,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
220,5
221,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
222,2
222,9
223,2
223,12
224,2
224,12
225,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
225,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
226,2
227,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
228,5
229,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
230,2
230,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
231,5
232,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
233,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
234,5
235,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
236,15
237,8
238,15
239,15
240,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
241,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
242,6
243,15
244,15
245,15
246,1
247,1
248,1
249,15
250,15
251,15
252,1
252,14
253,1
253,14
254,1
254,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
255,5
256,5
257,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
258,1
258,2
259,1
259,2
260,1
260,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
261,5
262,5
263,5
264,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
265,3
266,3
267,3
268,3
269,3
270,2
270,7
271,2
271,7
272,2
272,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
273,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
273,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
274,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
274,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
275,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
275,7
276,4
277,4
278,2
278,4
279,2
279,4
280,11
281,11
282,11
283,2
283,3
284,2
284,3
285,6
285,7
286,6
286,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
287,5
288,5
289,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
290,3
291,3
292,10
293,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
293,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
294,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
294,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
295,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
295,5
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
296,8
297,8
298,15
299,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
300,5
300,6
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
301,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
301,6
302,8
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
303,5
303,6
304,1
305,1
306,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
307,8
308,8
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
309,5
310,5
311,6
312,6
313,3
313,8
314,3
314,8
315,6
315,7
316,11
317,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
318,12
319,12
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
320,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
320,12
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
321,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
321,12
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
322,5
323,5
324,5
325,5
326,5
327,5
327,8
328,3
329,3
330,3
331,7
331,8
332,7
332,8
333,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
333,14
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
334,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
334,14
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
335,5
336,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
336,14
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
337,10
338,10
339,12
340,12
341,2
341,9
342,2
342,9
343,10
344,10
345,9
346,9
347,9
348,9
349,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
349,14
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
350,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
350,14
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
351,6
351,11
352,5
353,11
354,11
355,11
356,11
357,1
357,7
358,11
359,5
360,15
361,6
361,10
362,6
362,10
363,2
363,5
364,2
364,5
365,2
365,5
366,2
367,2
368,2
369,2
369,12
370,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
371,14
372,14
373,14
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
374,10
375,10
376,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
377,15
378,15
379,15
380,15
381,15
382,15
383,15
384,15
385,15
386,15
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
387,1
387,7
388,1
388,7
389,1
389,7
390,5
390,8
391,5
391,8
392,5
392,8
393,2
393,5
394,2
394,5
395,2
395,5
396,4
397,4
398,4
399,2
399,5
400,2
400,5
401,3
402,3
403,5
404,5
405,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
406,15
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
407,6
407,7
408,1
409,1
410,1
411,1
412,3
413,3
414,3
415,3
416,3
417,5
417,6
418,2
418,5
419,2
419,5
420,6
420,7
421,6
421,7
422,2
422,11
423,2
423,11
424,5
425,11
426,11
427,5
427,8
428,5
428,8
429,11
430,4
431,5
432,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
433,15
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
434,5
435,5
436,10
437,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
438,15
439,15
440,15
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
441,4
442,11
443,1
443,14
444,1
444,14
445,1
445,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
446,15
447,15
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
448,5
448,8
449,5
450,5
451,3
451,9
452,3
452,9
453,8
454,8
455,7
456,12
457,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
458,15
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
459,1
459,7
460,1
460,7
461,5
462,10
463,1
464,1
464,5
465,7
466,8
467,8
468,4
468,6
469,3
470,5
471,5
472,3
473,5
474,10
475,11
476,10
477,11
478,6
478,10
479,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
480,15
481,15
482,15
483,15
484,15
485,15
486,15
487,15
488,15
Fixed csvexport to write in primary key order. Good news: This no longer relies on InnoDB's default row order. Bad news: InnoDB in MySQL 5.0 has a bug where it will sort rows physically according to a secondary index, if there's a composite primary key and a single-column index and the phase of the moon is right. So a couple tables have been, once again, reordered -- but correctly this time. Good news: This bug will no longer fuck me up!
2009-07-27 05:19:27 +00:00
489,2
489,6
490,2
490,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
491,15
492,15
493,15
B&W: Added all new Pokémon! Forms now start at 10001.
2010-09-19 05:52:19 +00:00
494,15
495,5
495,7
496,5
496,7
497,5
497,7
498,5
499,5
500,5
501,5
502,5
503,5
504,5
505,5
506,5
507,5
508,5
509,5
510,5
511,5
512,5
513,5
514,5
515,5
516,5
517,5
518,5
519,4
520,4
521,4
522,5
523,5
524,10
525,10
526,10
527,4
527,5
528,4
528,5
529,5
530,5
531,6
532,8
533,8
534,8
535,2
536,2
537,2
538,8
539,8
540,3
541,3
542,3
543,3
544,3
545,3
546,6
546,7
547,6
547,7
548,7
549,7
550,12
551,5
552,5
553,5
554,5
555,5
556,7
557,3
557,10
558,3
558,10
559,5
559,14
560,5
560,14
561,4
562,10
562,11
563,10
563,11
564,2
564,9
565,2
565,9
566,4
566,9
567,4
567,9
568,10
569,10
570,5
571,5
572,5
573,5
574,8
575,8
576,8
577,11
578,11
579,11
580,2
580,4
581,2
581,4
582,10
583,10
584,10
585,5
586,5
587,5
588,3
589,3
590,7
591,7
592,11
593,11
594,2
594,12
595,3
596,3
597,7
597,10
598,7
598,10
599,10
600,10
601,10
602,11
603,11
604,11
605,8
606,8
607,11
608,11
609,11
610,1
610,14
611,1
611,14
612,1
612,14
613,5
614,5
615,10
616,3
617,3
618,2
618,11
619,5
619,8
620,5
620,8
621,1
621,14
622,10
623,10
624,8
625,8
626,5
627,4
628,4
629,4
630,4
631,5
632,3
633,14
634,14
635,14
636,3
637,3
638,15
639,15
640,15
641,15
642,15
643,15
644,15
645,15
646,15
647,15
648,15
649,15
Add egg groups for new Pokémon. I'm kind of confused about these. These data (which I got from Showdown, again) include egg groups for Carbink, which is genderless; I have heard that the official guide lists egg groups, but then Pumpkaboo and Gourgeist aren't listed as being in Grass, which is... very suspicious. Hm.
2013-11-05 17:05:17 +00:00
650,5
651,5
652,5
653,5
654,5
655,5
656,2
657,2
658,2
659,5
660,5
661,4
662,4
663,4
664,3
665,3
666,3
667,5
668,5
669,6
670,6
671,6
672,5
673,5
674,5
674,8
675,5
675,8
676,5
677,5
678,5
679,10
680,10
681,10
682,6
683,6
684,6
685,6
686,2
686,12
687,2
687,12
688,9
689,9
690,2
690,14
691,2
691,14
692,2
692,9
693,2
693,9
694,1
694,14
695,1
695,14
696,1
696,14
697,1
697,14
698,1
699,1
700,5
701,8
702,5
702,6
703,6
703,10
704,14
705,14
706,14
707,10
708,7
708,11
709,7
709,11
710,11
711,11
712,1
713,1
714,4
715,4
716,15
717,15
718,15
Reference in a new issue Copy permalink