OC Coding Style - Versionsgeschichte

Kratenko: fixed some syntax errors at ends of SQL-Strings

2016-08-29T12:28:27Z

fixed some syntax errors at ends of SQL-Strings

← Nächstältere Version		Version vom 29. August 2016, 12:28 Uhr
Zeile 29:		Zeile 29:
	FROM `caches`		FROM `caches`
	JOIN `cache_logs` ON `cache_logs`.`cache_id` = `caches`.`cache_id`		JOIN `cache_logs` ON `cache_logs`.`cache_id` = `caches`.`cache_id`
	WHERE `caches`.`status` IN ('&1', '&2')"		WHERE `caches`.`status` IN ('&1', '&2')",
	$status1,		$status1,
	$status2		$status2
Zeile 50:		Zeile 50:
	WHERE		WHERE
	`caches`.`status` = '&2'		`caches`.`status` = '&2'
	AND `cache_logs`.`user_id` = '&3'		AND `cache_logs`.`user_id` = '&3'",
	$logType,		$logType,
	$cacheStatus,		$cacheStatus,

Following: /* SQL */

2016-05-21T14:02:23Z

SQL

← Nächstältere Version		Version vom 21. Mai 2016, 14:02 Uhr
Zeile 36:		Zeile 36:
	Note that the opening " is on a tab position, while the following lines start one column to the right.		Note that the opening " is on a tab position, while the following lines start one column to the right.

	If lines get too long, the parameters are moved to the next line(s) and indented to the next indent column (which is ''three'' chars right of the preceding line ~~start~~):		If lines get too long, the parameters are moved to the next line(s) and indented to the next indent column (which is ''three'' chars right of the preceding line's keyword):

	$result = sql(		$result = sql(

Following: /* PHP */

2016-05-21T14:00:33Z

PHP

← Nächstältere Version		Version vom 21. Mai 2016, 14:00 Uhr
Zeile 13:		Zeile 13:
	All contributed or modified code sections must fully comply to the [http://www.php-fig.org/psr/psr-2/ PSR-2] standard (which includes [http://www.php-fig.org/psr/psr-1/ PSR-1]), with these exceptions:		All contributed or modified code sections must fully comply to the [http://www.php-fig.org/psr/psr-2/ PSR-2] standard (which includes [http://www.php-fig.org/psr/psr-1/ PSR-1]), with these exceptions:

	* When referencing identifiers (e.g. class and function names) that are defined in non-PSR-2-compliant source code files, ~~they~~ need not be PSR-2 compliant.		* When referencing identifiers (e.g. class and function names) that are defined in non-PSR-2-compliant source code files, their names need not be PSR-2 compliant.
	* When writing standalone scripts like those in the 'local', 'util' and 'util2' directories, they need not to comply to the PSR-1 "Side Effects" rule.		* When writing standalone scripts like those in the 'local', 'util' and 'util2' directories, they need not to comply to the PSR-1 "Side Effects" rule.

Following: /* SQL */

2016-05-21T13:34:41Z

SQL

← Nächstältere Version		Version vom 21. Mai 2016, 13:34 Uhr
Zeile 36:		Zeile 36:
	Note that the opening " is on a tab position, while the following lines start one column to the right.		Note that the opening " is on a tab position, while the following lines start one column to the right.

	If lines get too long, the parameters are moved to the next line(s) and indented to the next ~~Tab position~~ (which is ''three'' chars right of the preceding line start):		If lines get too long, the parameters are moved to the next line(s) and indented to the next indent column (which is ''three'' chars right of the preceding line start):

	$result = sql(		$result = sql(

Following am 19. Mai 2016 um 16:50 Uhr

2016-05-19T16:50:21Z

← Nächstältere Version		Version vom 19. Mai 2016, 16:50 Uhr
Zeile 57:		Zeile 57:

	[[Kategorie:Entwicklung\|Coding Style]]		[[Kategorie:Entwicklung\|Coding Style]]
			[[Kategorie:English pages]]

Following: /* PHP */

2016-05-19T16:40:40Z

PHP

← Nächstältere Version		Version vom 19. Mai 2016, 16:40 Uhr
Zeile 11:		Zeile 11:

	== PHP ==		== PHP ==
	All contributed or modified code sections must fully comply to the [http://www.php-fig.org/psr/psr-1/ PSR-1] / [http://www.php-fig.org/psr/psr-2/ PSR-2] ~~standard~~, with these exceptions:		All contributed or modified code sections must fully comply to the [http://www.php-fig.org/psr/psr-2/ PSR-2] standard (which includes [http://www.php-fig.org/psr/psr-1/ PSR-1]), with these exceptions:

	* When referencing identifiers (e.g. class and function names) that are defined in non-PSR-2-compliant source code files, they need not be PSR-2 compliant.		* When referencing identifiers (e.g. class and function names) that are defined in non-PSR-2-compliant source code files, they need not be PSR-2 compliant.

Following: /* PHP */

2016-05-19T16:22:13Z

PHP

← Nächstältere Version		Version vom 19. Mai 2016, 16:22 Uhr
Zeile 14:		Zeile 14:

	* When referencing identifiers (e.g. class and function names) that are defined in non-PSR-2-compliant source code files, they need not be PSR-2 compliant.		* When referencing identifiers (e.g. class and function names) that are defined in non-PSR-2-compliant source code files, they need not be PSR-2 compliant.
	* When writing ~~small~~ standalone scripts like those in the 'local' and '~~util~~' directories, they need not to comply to the PSR-1 "Side Effects" rule.		* When writing standalone scripts like those in the 'local', 'util' and 'util2' directories, they need not to comply to the PSR-1 "Side Effects" rule.

	Only <code><?php</code> and <code><?=</code> open tags must be used. <code><?</code> (short open tags) must not be used.		Only <code><?php</code> and <code><?=</code> open tags must be used. <code><?</code> (short open tags) must not be used.

Following: /* SQL */

2016-05-19T16:21:13Z

SQL

← Nächstältere Version		Version vom 19. Mai 2016, 16:21 Uhr
Zeile 34:		Zeile 34:
	);		);

	Note that the ~~starting~~ " is on a tab position, while the following lines start one column to the right.		Note that the opening " is on a tab position, while the following lines start one column to the right.

	If lines get too long, the parameters are moved to the next line(s) and indented to the next Tab position (which is ''three'' chars right of the preceding line start):		If lines get too long, the parameters are moved to the next line(s) and indented to the next Tab position (which is ''three'' chars right of the preceding line start):
Zeile 49:		Zeile 49:
	AND `cache_logs`.`type` = '&1'		AND `cache_logs`.`type` = '&1'
	WHERE		WHERE
	`caches`.`status` = '&1'		`caches`.`status` = '&2'
	AND `cache_logs`.`user_id` = '&2'		AND `cache_logs`.`user_id` = '&3'
			$logType,
	$cacheStatus,		$cacheStatus,
	$userId		$userId

Following: /* PHP */

2016-05-19T16:19:05Z

PHP

← Nächstältere Version		Version vom 19. Mai 2016, 16:19 Uhr
Zeile 11:		Zeile 11:

	== PHP ==		== PHP ==
	All contributed or modified code must fully comply to the [http://www.php-fig.org/psr/psr-1/ PSR-1] / [http://www.php-fig.org/psr/psr-2/ PSR-2] standard, with these exceptions:		All contributed or modified code sections must fully comply to the [http://www.php-fig.org/psr/psr-1/ PSR-1] / [http://www.php-fig.org/psr/psr-2/ PSR-2] standard, with these exceptions:

	* When referencing identifiers (e.g. class and function names) that are defined in non-PSR-2-compliant source code files, they need not be PSR-2 compliant.		* When referencing identifiers (e.g. class and function names) that are defined in non-PSR-2-compliant source code files, they need not be PSR-2 compliant.

Following am 19. Mai 2016 um 16:15 Uhr

2016-05-19T16:15:18Z

← Nächstältere Version		Version vom 19. Mai 2016, 16:15 Uhr
Zeile 11:		Zeile 11:

	== PHP ==		== PHP ==
	All ~~self-written~~ or ~~directly changed~~ code must fully comply to the [http://www.php-fig.org/psr/psr-1/ PSR-1] / [http://www.php-fig.org/psr/psr-2/ PSR-2] standard, with these exceptions:		All contributed or modified code must fully comply to the [http://www.php-fig.org/psr/psr-1/ PSR-1] / [http://www.php-fig.org/psr/psr-2/ PSR-2] standard, with these exceptions:

	* When referencing identifiers (e.g. class and function names) that are defined in non-PSR-2-compliant source code files, they need not be PSR-2 compliant.		* When referencing identifiers (e.g. class and function names) that are defined in non-PSR-2-compliant source code files, they need not be PSR-2 compliant.
Zeile 28:		Zeile 28:
	"SELECT `cache_id`, `wp_oc`		"SELECT `cache_id`, `wp_oc`
	FROM `caches`		FROM `caches`
	JOIN `cache_logs` ON `cache_logs`.`id` = `caches`.`id`		JOIN `cache_logs` ON `cache_logs`.`cache_id` = `caches`.`cache_id`
	WHERE `caches`.`status` IN ('&1', '&2')"		WHERE `caches`.`status` IN ('&1', '&2')"
	$status1,		$status1,
Zeile 43:		Zeile 43:
	`caches`.`type` AS `cache_type`,		`caches`.`type` AS `cache_type`,
	`cache_logs`.`date` AS `log_date`,		`cache_logs`.`date` AS `log_date`,
	`cache_logs`.`type` AS `log_type`,		`cache_logs`.`type` AS `log_type`
	FROM `caches`		FROM `caches`
	JOIN `cache_logs`		JOIN `cache_logs`
	ON `cache_logs`.`id` = `caches`.`id`		ON `cache_logs`.`cache_id` = `caches`.`cache_id`
	AND `cache_logs`.`type` = '&1'		AND `cache_logs`.`type` = '&1'
	WHERE		WHERE
	`caches`.`status` = '&1'		`caches`.`status` = '&1'
	AND `cache_logs`.`user_id` = '&2'		AND `cache_logs`.`user_id` = '&2'
	$cacheStatus		$cacheStatus,
	$userId		$userId
	);		);

			[[Kategorie:Entwicklung\|Coding Style]]