Failed Conditions
Pull Request — master (#353)
by Florian
04:36 queued 02:02
created

QueryManagerMysqlMonocleAlternate::getTotalLures()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4
Code Lines 3

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 1
eloc 3
nc 1
nop 0
dl 0
loc 4
rs 10
c 0
b 0
f 0
1
<?php
2
3
class QueryManagerMysqlMonocleAlternate extends QueryManagerMysql {
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
4
5
	public function __construct() {
6
		parent::__construct();
7
	}
8
9
	public function __destruct() {
10
		parent::__destruct();
11
	}
12
13
	///////////
14
	// Tester
15
	///////////
16
17 View Code Duplication
	function testTotalPokemon() {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for testTotalPokemon.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
18
		$req = "SELECT COUNT(*) as total FROM sightings";
19
		$result = $this->mysqli->query($req);
20
		if (!is_object($result)) {
21
			return 1;
22
		} else {
23
			$data = $result->fetch_object();
24
			$total = $data->total;
25
26
			if ($total == 0) {
27
				return 2;
28
			}
29
		}
30
		return 0;
31
	}
32
33 View Code Duplication
	function testTotalGyms() {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for testTotalGyms.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
34
		$req = "SELECT COUNT(*) as total FROM forts";
35
		$result = $this->mysqli->query($req);
36
		if (!is_object($result)) {
37
			return 1;
38
		} else {
39
			$data = $result->fetch_object();
40
			$total = $data->total;
41
42
			if ($total == 0) {
43
				return 2;
44
			}
45
		}
46
		return 0;
47
	}
48
49 View Code Duplication
	function testTotalPokestops() {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for testTotalPokestops.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
50
		$req = "SELECT COUNT(*) as total FROM pokestops";
51
		$result = $this->mysqli->query($req);
52
		if (!is_object($result)) {
53
			return 1;
54
		} else {
55
			$data = $result->fetch_object();
56
			$total = $data->total;
57
58
			if ($total == 0) {
59
				return 2;
60
			}
61
		}
62
		return 0;
63
	}
64
	
65
	
66
	/////////////
67
	// Homepage
68
	/////////////
69
70
	function getTotalPokemon() {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getTotalPokemon.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
71
		$req = "SELECT COUNT(*) AS total FROM sightings WHERE expire_timestamp >= UNIX_TIMESTAMP()";
72
		$result = $this->mysqli->query($req);
73
		$data = $result->fetch_object();
74
		return $data;
75
	}
76
77
	function getTotalLures() {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getTotalLures.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
78
		$data = (object) array("total" => 0);
79
		return $data;
80
	}
81
82
	function getTotalGyms() {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getTotalGyms.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
83
		$req = "SELECT COUNT(*) AS total FROM forts";
84
		$result = $this->mysqli->query($req);
85
		$data = $result->fetch_object();
86
		return $data;
87
	}
88
89
	function getTotalRaids() {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getTotalRaids.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
90
		$req = "SELECT COUNT(*) AS total FROM raids WHERE time_battle <= UNIX_TIMESTAMP() AND time_end >= UNIX_TIMESTAMP()";
91
		$result = $this->mysqli->query($req);
92
		$data = $result->fetch_object();
93
		return $data;
94
	}
95
96
97
	function getTotalGymsForTeam($team_id) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getTotalGymsForTeam.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
98
		$req = "SELECT COUNT(*) AS total FROM fort_sightings WHERE team = '$team_id'";
99
		$result = $this->mysqli->query($req);
100
		$data = $result->fetch_object();
101
		return $data;
102
	}
103
104
	function getRecentAll() {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getRecentAll.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
105
		$req = "SELECT DISTINCT pokemon_id, encounter_id, FROM_UNIXTIME(expire_timestamp) AS disappear_time, FROM_UNIXTIME(updated) AS last_modified, FROM_UNIXTIME(expire_timestamp) AS disappear_time_real,
106
              lat AS latitude, lon AS longitude, cp, atk_iv AS individual_attack, def_iv AS individual_defense, sta_iv AS individual_stamina
107
              FROM sightings
108
              ORDER BY last_modified DESC
109
              LIMIT 0,12";
110
		$result = $this->mysqli->query($req);
111
		$data = array();
112
		if ($result->num_rows > 0) {
113
			while ($row = $result->fetch_object()) {
114
				$data[] = $row;
115
			}
116
		}
117
		return $data;
118
	}
119
120
	function getRecentMythic($mythic_pokemon) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getRecentMythic.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
121
		$req = "SELECT pokemon_id, encounter_id, FROM_UNIXTIME(expire_timestamp) AS disappear_time, FROM_UNIXTIME(updated) AS last_modified, FROM_UNIXTIME(expire_timestamp) AS disappear_time_real,
122
                lat AS latitude, lon AS longitude, cp, atk_iv AS individual_attack, def_iv AS individual_defense, sta_iv AS individual_stamina
123
                FROM sightings
124
                WHERE pokemon_id IN (".implode(",", $mythic_pokemon).")
125
                ORDER BY updated DESC
126
                LIMIT 0,12";
127
		$result = $this->mysqli->query($req);
128
		$data = array();
129
		if ($result->num_rows > 0) {
130
			while ($row = $result->fetch_object()) {
131
				$data[] = $row;
132
			}
133
		}
134
		return $data;
135
	}
136
137
	///////////////////
138
	// Single Pokemon
139
	///////////////////
140
141 View Code Duplication
	function getGymsProtectedByPokemon($pokemon_id) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getGymsProtectedByPokemon.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
142
		$req = "SELECT COUNT(DISTINCT(fort_id)) AS total FROM fort_sightings WHERE guard_pokemon_id = '".$pokemon_id."'";
143
		$result = $this->mysqli->query($req);
144
		$data = $result->fetch_object();
145
		return $data;
146
	}
147
148 View Code Duplication
	function getPokemonLastSeen($pokemon_id) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getPokemonLastSeen.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
149
		$req = "SELECT FROM_UNIXTIME(expire_timestamp) AS expire_timestamp, FROM_UNIXTIME(expire_timestamp) AS disappear_time_real, lat AS latitude, lon AS longitude
150
                FROM sightings
151
                WHERE pokemon_id = '".$pokemon_id."'
152
                ORDER BY expire_timestamp DESC
153
                LIMIT 0,1";
154
		$result = $this->mysqli->query($req);
155
		$data = $result->fetch_object();
156
		return $data;
157
	}
158
159
	function getTop50Pokemon($pokemon_id, $top_order_by, $top_direction) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getTop50Pokemon.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
160
		$req = "SELECT FROM_UNIXTIME(expire_timestamp) AS distime, pokemon_id as pokemon_id, FROM_UNIXTIME(expire_timestamp) as disappear_time, lat as latitude, lon as longitude,
161
                cp, atk_iv as individual_attack, def_iv as individual_defense, sta_iv as individual_stamina,
162
                ROUND(100*(atk_iv+def_iv+sta_iv)/45,1) AS IV, move_1 as move_1, move_2, form
163
                FROM sightings
164
	            WHERE pokemon_id = '" . $pokemon_id . "' AND move_1 IS NOT NULL AND move_1 <> '0'
165
	            ORDER BY $top_order_by $top_direction, expire_timestamp DESC
166
	            LIMIT 0,50";
167
168
		$result = $this->mysqli->query($req);
169
		$top = array();
170
		while ($data = $result->fetch_object()) {
171
			$top[] = $data;
172
		}
173
		return $top;
174
	}
175
176 View Code Duplication
	function getTop50Trainers($pokemon_id, $best_order_by, $best_direction) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getTop50Trainers.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
177
		$trainer_blacklist = "";
178
		if (!empty(self::$config->system->trainer_blacklist)) {
179
			$trainer_blacklist = " AND owner_name NOT IN ('" . implode("','", self::$config->system->trainer_blacklist) . "')";
180
		}
181
182
		$req = "SELECT owner_name as trainer_name, ROUND((100*((atk_iv)+(def_iv)+(sta_iv))/45),1) AS IV, move_1, move_2, cp as cp,
183
                FROM_UNIXTIME(last_modified) AS lasttime, last_modified as last_seen
184
                FROM gym_defenders
185
				WHERE pokemon_id = '" . $pokemon_id . "'" . $trainer_blacklist . "
186
				ORDER BY $best_order_by $best_direction, owner_name ASC
187
				LIMIT 0,50";
188
189
		$result = $this->mysqli->query($req);
190
		$toptrainer = array();
191
		while ($data = $result->fetch_object()) {
192
			$toptrainer[] = $data;
193
		}
194
		return $toptrainer;
195
	}
196
197 View Code Duplication
	public function getPokemonHeatmap($pokemon_id, $start, $end) {
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
198
		$where = " WHERE pokemon_id = ".$pokemon_id." "
199
			. "AND FROM_UNIXTIME(expire_timestamp) BETWEEN '".$start."' AND '".$end."'";
200
		$req 		= "SELECT lat AS latitude, lon AS longitude FROM sightings".$where." ORDER BY expire_timestamp DESC LIMIT 100000";
201
		$result = $this->mysqli->query($req);
202
		$points = array();
203
		while ($data = $result->fetch_object()) {
204
			$points[] = $data;
205
		}
206
		return $points;
207
	}
208
209 View Code Duplication
	public function getPokemonGraph($pokemon_id) {
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
210
		$req = "SELECT COUNT(*) AS total, HOUR(disappear_time) AS disappear_hour
211
					FROM (SELECT FROM_UNIXTIME(expire_timestamp) as disappear_time FROM sightings WHERE pokemon_id = '".$pokemon_id."' ORDER BY disappear_time LIMIT 100000) AS pokemonFiltered
212
				GROUP BY disappear_hour
213
				ORDER BY disappear_hour";
214
		$result = $this->mysqli->query($req);
215
		$array = array_fill(0, 24, 0);
216
		while ($result && $data = $result->fetch_object()) {
217
			$array[$data->disappear_hour] = $data->total;
218
		}
219
		// shift array because AM/PM starts at 1AM not 0:00
220
		$array[] = $array[0];
221
		array_shift($array);
222
		return $array;
223
	}
224
225 View Code Duplication
	public function getPokemonLive($pokemon_id, $ivMin, $ivMax, $inmap_pokemons) {
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
226
		$inmap_pkms_filter = "";
227
		$where = " WHERE expire_timestamp >= UNIX_TIMESTAMP() AND pokemon_id = " . $pokemon_id;
228
229
		$reqTestIv = "SELECT MAX(atk_iv) AS iv FROM sightings " . $where;
230
		$resultTestIv = $this->mysqli->query($reqTestIv);
231
		$testIv = $resultTestIv->fetch_object();
232
		if (!is_null($inmap_pokemons) && ($inmap_pokemons != "")) {
233
			foreach ($inmap_pokemons as $inmap) {
234
				$inmap_pkms_filter .= "'".$inmap."',";
235
			}
236
			$inmap_pkms_filter = rtrim($inmap_pkms_filter, ",");
237
			$where .= " AND encounter_id NOT IN (" . $inmap_pkms_filter . ") ";
238
		}
239
		if ($testIv->iv != null && !is_null($ivMin) && ($ivMin != "")) {
240
			$where .= " AND ((100/45)*(atk_iv + def_iv + sta_iv)) >= (" . $ivMin . ") ";
241
		}
242
		if ($testIv->iv != null && !is_null($ivMax) && ($ivMax != "")) {
243
			$where .= " AND ((100/45)*(atk_iv + def_iv + sta_iv)) <= (" . $ivMax . ") ";
244
		}
245
		$req = "SELECT pokemon_id, lat AS latitude, lon AS longitude,
246
    					FROM_UNIXTIME(expire_timestamp) AS disappear_time,
247
    					FROM_UNIXTIME(expire_timestamp) AS disappear_time_real,
248
    					atk_iv AS individual_attack, def_iv AS individual_defense, sta_iv AS individual_stamina,
249
   						move_1, move_2
250
					FROM sightings " . $where . "
251
					ORDER BY disappear_time DESC
252
					LIMIT 5000";
253
		$result = $this->mysqli->query($req);
254
		$spawns = array();
255
		while ($data = $result->fetch_object()) {
256
			$spawns[] = $data;
257
		}
258
		return $spawns;
259
	}
260
261
	public function getPokemonSliderMinMax() {
262
		$req = "SELECT FROM_UNIXTIME(MIN(expire_timestamp)) AS min, FROM_UNIXTIME(MAX(expire_timestamp)) AS max FROM sightings";
263
		$result = $this->mysqli->query($req);
264
		$data = $result->fetch_object();
265
		return $data;
266
	}
267
268
	public function getMapsCoords() {
269
		$req = "SELECT MAX(lat) AS max_latitude, MIN(lat) AS min_latitude, MAX(lon) AS max_longitude, MIN(lon) as min_longitude FROM spawnpoints";
270
		$result = $this->mysqli->query($req);
271
		$data = $result->fetch_object();
272
		return $data;
273
	}
274
275
276
	///////////////
277
	// Pokestops
278
	//////////////
279
280
281
	function getTotalPokestops() {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getTotalPokestops.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
282
		$req = "SELECT COUNT(*) as total FROM pokestops";
283
		$result = $this->mysqli->query($req);
284
		$data = $result->fetch_object();
285
		return $data;
286
	}
287
288
	public function getAllPokestops() {
289
		$req = "SELECT lat as latitude, lon as longitude, null AS lure_expiration, UNIX_TIMESTAMP() AS now, null AS lure_expiration_real FROM pokestops";
290
		$result = $this->mysqli->query($req);
291
		$pokestops = array();
292
		while ($data = $result->fetch_object()) {
293
			$pokestops[] = $data;
294
		}
295
		return $pokestops;
296
	}
297
298
299
	/////////
300
	// Gyms
301
	/////////
302
303
	function getTeamGuardians($team_id) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getTeamGuardians.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
304
		$req = "SELECT COUNT(*) AS total, guard_pokemon_id FROM fort_sightings WHERE team = '".$team_id."' GROUP BY guard_pokemon_id ORDER BY total DESC LIMIT 0,3";
305
		$result = $this->mysqli->query($req);
306
307
		$datas = array();
308
		while ($data = $result->fetch_object()) {
309
			$datas[] = $data;
310
		}
311
312
		return $datas;
313
	}
314
315
	function getOwnedAndPoints($team_id) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getOwnedAndPoints.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
316
		$req = "SELECT COUNT(DISTINCT(fs.fort_id)) AS total, ROUND((SUM(gd.cp)) / COUNT(DISTINCT(fs.fort_id)),0) AS average_points
317
        			FROM fort_sightings fs
318
        			JOIN gym_defenders gd ON fs.fort_id = gd.fort_id
319
        			WHERE fs.team = '" . $team_id . "'";
320
		$result = $this->mysqli->query($req);
321
		$data = $result->fetch_object();
322
		return $data;
323
	}
324
325
	function getAllGyms() {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
Comprehensibility Best Practice introduced by
It is recommend to declare an explicit visibility for getAllGyms.

Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed.

If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with private, and only raise it to protected if a sub-class needs to have access, or public if an external class needs access.

Loading history...
326
		$req = "SELECT f.id as gym_id, team as team_id, f.lat as latitude, f.lon as longitude, updated as last_scanned, (6 - fs.slots_available) AS level FROM forts f LEFT JOIN fort_sightings fs ON f.id = fs.fort_id;";
327
		$result = $this->mysqli->query($req);
328
		$gyms = array();
329
		while ($data = $result->fetch_object()) {
330
			$gyms[] = $data;
331
		}
332
		return $gyms;
333
	}
334
335
	public function getGymData($gym_id) {
336
		$req = "SELECT f.name AS name, null AS description, f.url AS url, fs.team AS team, FROM_UNIXTIME(fs.updated) AS last_scanned, fs.guard_pokemon_id AS guard_pokemon_id, (6 - fs.slots_available) AS level, SUM(gd.cp) as total_cp	
337
			FROM fort_sightings fs
338
			LEFT JOIN forts f ON f.id = fs.fort_id
339
			LEFT JOIN gym_defenders gd ON f.id = gd.fort_id
340
			WHERE f.id ='".$gym_id."'
341
			GROUP BY f.name, f.url, fs.team, fs.updated, fs.guard_pokemon_id, fs.slots_available, gd.cp";
342
		$result = $this->mysqli->query($req);
343
		$data = $result->fetch_object();
344
		return $data;
345
	}
346
347
	public function getGymDefenders($gym_id) {
348
		$req = "SELECT DISTINCT external_id as pokemon_uid, pokemon_id, atk_iv as iv_attack, def_iv as iv_defense, sta_iv as iv_stamina, cp, fort_id as gym_id
349
			FROM gym_defenders 
350
			WHERE fort_id='".$gym_id."'
351
			ORDER BY cp DESC";
352
		$result = $this->mysqli->query($req);
353
		$defenders = array();
354
		while ($data = $result->fetch_object()) {
355
			$defenders[] = $data;
356
		}
357
		return $defenders;
358
	}
359
360
361
	///////////
362
	// Raids
363
	///////////
364
365 View Code Duplication
	public function getAllRaids($page) {
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
366
		$limit = " LIMIT ".($page * 10).",10";
367
		$req = "SELECT r.fort_id AS gym_id, r.level AS level, r.pokemon_id AS pokemon_id, r.cp AS cp, r.move_1 AS move_1, r.move_2 AS move_2, FROM_UNIXTIME(r.time_spawn) AS spawn, FROM_UNIXTIME(r.time_battle) AS start, FROM_UNIXTIME(r.time_end) AS end, FROM_UNIXTIME(fs.updated) AS last_scanned, f.name, f.lat AS latitude, f.lon as longitude 
368
					FROM raids r 
369
					JOIN forts f ON f.id = r.fort_id 
370
					LEFT JOIN fort_sightings fs ON fs.fort_id = r.fort_id 
371
					WHERE r.time_end > UNIX_TIMESTAMP() 
372
					ORDER BY r.level DESC, r.time_battle" . $limit;
373
		$result = $this->mysqli->query($req);
374
		$raids = array();
375
		while ($data = $result->fetch_object()) {
376
			$raids[] = $data;
377
		}
378
		return $raids;
379
	}
380
381
382
383
	////////////////
384
	// Gym History
385
	////////////////
386
387
	public function getGymHistories($gym_name, $team, $page, $ranking)
388
	{
389
		// TODO: Implement
390
		return array();
391
	}
392
393
	public function getGymHistoriesPokemon($gym_id)
394
	{
395
		// TODO: Implement
396
		return array();
397
	}
398
399
	public function getHistoryForGym($page, $gym_id)
400
	{
401
		// TODO: Implement
402
		return array();
403
	}
404
405
	public function getHistoryForGymPokemon($pkm_uids)
406
	{
407
		// TODO: Implement
408
		return array();
409
	}
410
411
412
413
	//////////////
414
	// Trainers
415
	//////////////
416
417
	public function getTrainers($trainer_name, $team, $page, $ranking) {
418
		return array(); // Waiting for Monocle to store level
419
	}
420
421 View Code Duplication
	public function getTrainerLevelCount($team_id) {
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
422
		$levelData = array();
423
		for ($i = 5; $i <= 40; $i++) {
424
			if (!isset($levelData[$i])) {
425
				$levelData[$i] = 0;
426
			}
427
		}
428
		return $levelData; // Waiting for Monocle to store level
429
	}
430
431
432
	/////////
433
	// Cron
434
	/////////
435
436
	public function getPokemonCountsActive() {
437
		$req = "SELECT pokemon_id, COUNT(*) as total FROM sightings WHERE expire_timestamp >= UNIX_TIMESTAMP() GROUP BY pokemon_id";
438
		$result = $this->mysqli->query($req);
439
		$counts = array();
440
		while ($data = $result->fetch_object()) {
441
			$counts[$data->pokemon_id] = $data->total;
442
		}
443
		return $counts;
444
	}
445
446
	public function getPokemonCountsLastDay() {
447
		$req = "SELECT pokemon_id, COUNT(*) AS spawns_last_day
448
					FROM sightings
449
					WHERE expire_timestamp >= (SELECT MAX(expire_timestamp) - 86400 FROM sightings)
450
					GROUP BY pokemon_id
451
				  	ORDER BY pokemon_id ASC";
452
		$result = $this->mysqli->query($req);
453
		$counts = array();
454
		while ($data = $result->fetch_object()) {
455
			$counts[$data->pokemon_id] = $data->spawns_last_day;
456
		}
457
		return $counts;
458
	}
459
460 View Code Duplication
	public function getPokemonSinceLastUpdate($pokemon_id, $last_update) {
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
461
		$where = "WHERE p.pokemon_id = '".$pokemon_id."' AND p.expire_timestamp - (coalesce(CASE WHEN duration = 0 THEN NULL ELSE duration END ,30)*60) > '".$last_update."'";
462
		$req = "SELECT count, p.expire_timestamp - (coalesce(CASE WHEN duration = 0 THEN NULL ELSE duration END ,30)*60) AS last_timestamp, (FROM_UNIXTIME(p.expire_timestamp)) AS disappear_time_real, p.lat as latitude, p.lon as longitude
463
					FROM sightings p
464
					LEFT JOIN spawnpoints s ON p.spawn_id = s.spawn_id
465
					JOIN (SELECT COUNT(*) AS count
466
						FROM sightings p
467
						LEFT JOIN spawnpoints s ON p.spawn_id = s.spawn_id
468
                    	" . $where."
469
                    ) x
470
					" . $where . "
471
					ORDER BY last_timestamp DESC
472
					LIMIT 0 , 1";
473
		$result = $this->mysqli->query($req);
474
		$data = $result->fetch_object();
475
		return $data;
476
	}
477
478 View Code Duplication
	public function getRaidsSinceLastUpdate($pokemon_id, $last_update) {
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
479
		$where = "WHERE pokemon_id = '".$pokemon_id."AND".$last_update."'";
480
		$req = "SELECT time_battle AS start_timestamp, time_end as end, (FROM_UNIXTIME(time_end)) AS end_time_real, lat as latitude, lon as longitude, count
481
					FROM raids r
482
					JOIN forts g
483
					JOIN (SELECT COUNT(*) AS count
484
						FROM raids
485
                    	" . $where."
486
                    ) x 
487
					ON r.fort_id = g.id
488
                    " . $where . "
489
                    ORDER BY time_battle DESC
490
					LIMIT 0 , 1";
491
		$result = $this->mysqli->query($req);
492
		$data = $result->fetch_object();
493
		return $data;
494
	}
495
496
	public function getCaptchaCount() {
497
		$req = " SELECT COUNT(*) as total FROM accounts WHERE captchaed IS NOT NULL AND reason IS NULL";
498
		$result = $this->mysqli->query($req);
499
		$data = $result->fetch_object();
500
		return $data;
501
	}
502
503 View Code Duplication
	public function getNestData() {
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
504
		$pokemon_exclude_sql = "";
505
		if (!empty(self::$config->system->nest_exclude_pokemon)) {
506
			$pokemon_exclude_sql = "AND p.pokemon_id NOT IN (" . implode(",", self::$config->system->nest_exclude_pokemon) . ")";
507
		}
508
		$req = "SELECT p.pokemon_id, MAX(p.lat) AS latitude, MAX(p.lon) AS longitude, count(p.pokemon_id) AS total_pokemon, MAX(s.updated) as latest_seen, coalesce(CASE WHEN MAX(duration) = 0 THEN NULL ELSE MAX(duration) END ,30)*60 as duration
509
			          FROM sightings p
510
			          INNER JOIN spawnpoints s ON (p.spawn_id = s.spawn_id)
511
			          WHERE p.expire_timestamp > UNIX_TIMESTAMP() - 86400
512
			          " . $pokemon_exclude_sql . "
513
			          GROUP BY p.spawn_id, p.pokemon_id
514
			          HAVING COUNT(p.pokemon_id) >= 6
515
			          ORDER BY p.pokemon_id";
516
		$result = $this->mysqli->query($req);
517
		$nests = array();
518
		while ($data = $result->fetch_object()) {
519
			$nests[] = $data;
520
		}
521
		return $nests;
522
	}
523
524
}
525