Game database model: dbmodel.sql - Гісторыя версій

PurplishCat на 15:42, 19 кастрычніка 2020

2020-10-19T15:42:39Z

← Папярэдн. версія		Версія ад 17:42, 19 кастрычніка 2020
Радок 26:		Радок 26:
	</pre>		</pre>

	~~For your information, the useful~~ columns of default "player" table are:		The commonly used columns of default "player" table are:
	* <strong>player_no</strong>: the index of player in natural playing order (starting with 1)		* <strong>player_no</strong>: the index of player in natural playing order (starting with 1)
	* <strong>player_id</strong>		* <strong>player_id</strong> (int)
	* <strong>player_name</strong>: (note: ~~you should~~ better access this date with getActivePlayerName() or loadPlayersBasicInfos() methods)<br/><br/>		* <strong>player_name</strong>: (note: it is better to access this date with getActivePlayerName() or loadPlayersBasicInfos() methods)<br/><br/>

	* <strong>player_score</strong>: the current score of the player (displayed in the player panel). You must update this field to update player's scores.		* <strong>player_score</strong>: the current score of the player (displayed in the player panel). You must update this field to update player's scores.
	* <strong>player_score_aux</strong>: the secondary score, used as a tie breaker. You must update this field according to tie breaking rules of the game (see also: [[Main_game_logic:_yourgamename.game.php#Manage_player_scores_and_Tie_breaker\|Manage_player_scores_and_Tie_breaker]])<br/><br/>		* <strong>player_score_aux</strong>: the secondary score, used as a tie breaker. You must update this field according to tie breaking rules of the game (see also: [[Main_game_logic:_yourgamename.game.php#Manage_player_scores_and_Tie_breaker\|Manage_player_scores_and_Tie_breaker]])<br/><br/>

	* <strong>player_table_order</strong>: gives an indication of the rank of the player by order of arrival in the lobby (starting with 1). It is not the same as player_no which is the player order <u>within</u> the game. This is useful to set custom teams if wished in a game option (for instance 1st-2nd vs 3rd-4th).<br /><strong><u>CAUTION:</u></strong> This value is currently <u>not ~~guaranted~~</u> to be actually equal with the rank of the player in the table. For example, in a 4 player game, if the table was full but the 3rd player have left before the game starts, the 4th player becomes 3rd on this table <u>but</u> their player_table_no is still equal to 4! If another player then joins, their player_table_no will then be 5...<br />Thus, it is essential to normalize these values first in the game setup if you wish to use them to prevent bugs at game launch. For example, if the set of player_table_order are <player A>: 3, <player B>: 2, <player C>: 5, <player D>: 7, you see that you can't read that values as ranks directly, but you can still deduce that <player B> was 1st on the table, then <player A> then <player C> then <player D> 😉		* <strong>player_table_order</strong>: gives an indication of the rank of the player by order of arrival in the lobby (starting with 1). It is not the same as player_no which is the player order <u>within</u> the game. This is useful to set custom teams if wished in a game option (for instance 1st-2nd vs 3rd-4th).<br /><strong><u>CAUTION:</u></strong> This value is currently <u>not guaranteed</u> to be actually equal with the rank of the player in the table. For example, in a 4 player game, if the table was full but the 3rd player have left before the game starts, the 4th player becomes 3rd on this table <u>but</u> their player_table_no is still equal to 4! If another player then joins, their player_table_no will then be 5...<br />Thus, it is essential to normalize these values first in the game setup if you wish to use them to prevent bugs at game launch. For example, if the set of player_table_order are <player A>: 3, <player B>: 2, <player C>: 5, <player D>: 7, you see that you can't read that values as ranks directly, but you can still deduce that <player B> was 1st on the table, then <player A> then <player C> then <player D> 😉

	== CREATE TABLES ==		== CREATE TABLES ==

Woodruff: /* Default tables */

2020-06-19T20:32:00Z

Default tables

← Папярэдн. версія		Версія ад 22:32, 19 чэрвеня 2020
Радок 34:		Радок 34:
	* <strong>player_score_aux</strong>: the secondary score, used as a tie breaker. You must update this field according to tie breaking rules of the game (see also: [[Main_game_logic:_yourgamename.game.php#Manage_player_scores_and_Tie_breaker\|Manage_player_scores_and_Tie_breaker]])<br/><br/>		* <strong>player_score_aux</strong>: the secondary score, used as a tie breaker. You must update this field according to tie breaking rules of the game (see also: [[Main_game_logic:_yourgamename.game.php#Manage_player_scores_and_Tie_breaker\|Manage_player_scores_and_Tie_breaker]])<br/><br/>

	* <strong>player_table_order</strong>: gives an indication of the rank of the player by order of arrival in the lobby (starting with 1). It is not the same as player_no which is the player order <u>within</u> the game. This is useful to set custom teams if wished in a game option (for instance 1st-2nd vs 3rd-4th).<br /><strong><u>CAUTION:</u></strong> This value is currently <u>not guaranted</u> to be actually equal with the rank of the player in the table. For example, in a 4 player game, if the table was full but the 3rd player have left before the game starts, the 4th player becomes 3rd on this table <u>but</u> their player_table_no is still equal to 4! If another player then joins, their player_table_no will then be 5...<br />Thus, it is essential to normalize these values first in the game setup if you wish to use them to prevent bugs at game launch. For example, if the set of player_table_order are <player A>: 3, <player B>: 2, <player C>: 5, <player D>: 7, you see that you can't read that values as ranks directly, but you can still deduce that <player B> was 1st on the table, then <player A> then <player C> then <player D> 😉		* <strong>player_table_order</strong>: gives an indication of the rank of the player by order of arrival in the lobby (starting with 1). It is not the same as player_no which is the player order <u>within</u> the game. This is useful to set custom teams if wished in a game option (for instance 1st-2nd vs 3rd-4th).<br /><strong><u>CAUTION:</u></strong> This value is currently <u>not guaranted</u> to be actually equal with the rank of the player in the table. For example, in a 4 player game, if the table was full but the 3rd player have left before the game starts, the 4th player becomes 3rd on this table <u>but</u> their player_table_no is still equal to 4! If another player then joins, their player_table_no will then be 5...<br />Thus, it is essential to normalize these values first in the game setup if you wish to use them to prevent bugs at game launch. For example, if the set of player_table_order are <player A>: 3, <player B>: 2, <player C>: 5, <player D>: 7, you see that you can't read that values as ranks directly, but you can still deduce that <player B> was 1st on the table, then <player A> then <player C> then <player D> 😉
	)

	== CREATE TABLES ==		== CREATE TABLES ==

Woodruff: /* Default tables */

2020-06-19T20:31:32Z

Default tables

← Папярэдн. версія		Версія ад 22:31, 19 чэрвеня 2020
Радок 34:		Радок 34:
	* <strong>player_score_aux</strong>: the secondary score, used as a tie breaker. You must update this field according to tie breaking rules of the game (see also: [[Main_game_logic:_yourgamename.game.php#Manage_player_scores_and_Tie_breaker\|Manage_player_scores_and_Tie_breaker]])<br/><br/>		* <strong>player_score_aux</strong>: the secondary score, used as a tie breaker. You must update this field according to tie breaking rules of the game (see also: [[Main_game_logic:_yourgamename.game.php#Manage_player_scores_and_Tie_breaker\|Manage_player_scores_and_Tie_breaker]])<br/><br/>

	* <strong>player_table_order</strong>: gives an indication of the rank of the player by order of arrival in the lobby (starting with 1). It is not the same as player_no which is the player order <u>within</u> the game. This is useful to set custom teams if wished in a game option (for instance 1st-2nd vs 3rd-4th).<br /><strong><u>CAUTION:</u></strong> This value is currently <u>not guaranted</u> to be actually equal with the rank of the player in the table. For example, in a 4 player game, if the table was full but the 3rd player have left before the game starts, the 4th player becomes 3rd on this table <u>but</u> their player_table_no is still equal to 4! If another player then joins, their player_table_no will then be 5...<br />Thus, it is essential to normalize these values first in the game setup if you wish to use them to prevent bugs at game launch. For example, if the set of player_table_order are <player A>: 3, <player B>: 2, <player C>: 5, <player D>: 7, you see that you can't read that values as ranks directly, but you can still deduce that <player B> was 1st on the table, then <player A> then <player C> then <player D> ~~<strong>~~;-)~~</strong>~~		* <strong>player_table_order</strong>: gives an indication of the rank of the player by order of arrival in the lobby (starting with 1). It is not the same as player_no which is the player order <u>within</u> the game. This is useful to set custom teams if wished in a game option (for instance 1st-2nd vs 3rd-4th).<br /><strong><u>CAUTION:</u></strong> This value is currently <u>not guaranted</u> to be actually equal with the rank of the player in the table. For example, in a 4 player game, if the table was full but the 3rd player have left before the game starts, the 4th player becomes 3rd on this table <u>but</u> their player_table_no is still equal to 4! If another player then joins, their player_table_no will then be 5...<br />Thus, it is essential to normalize these values first in the game setup if you wish to use them to prevent bugs at game launch. For example, if the set of player_table_order are <player A>: 3, <player B>: 2, <player C>: 5, <player D>: 7, you see that you can't read that values as ranks directly, but you can still deduce that <player B> was 1st on the table, then <player A> then <player C> then <player D> 😉
			)

	== CREATE TABLES ==		== CREATE TABLES ==

Woodruff: /* Default tables */

2020-06-19T20:30:22Z

Default tables

← Папярэдн. версія		Версія ад 22:30, 19 чэрвеня 2020
Радок 27:		Радок 27:

	For your information, the useful columns of default "player" table are:		For your information, the useful columns of default "player" table are:
	* player_no: the index of player in natural playing order.		* <strong>player_no</strong>: the index of player in natural playing order (starting with 1)
	* player_id		* <strong>player_id</strong>
	* player_name: (note: you should better access this date with getActivePlayerName() or loadPlayersBasicInfos() methods)		* <strong>player_name</strong>: (note: you should better access this date with getActivePlayerName() or loadPlayersBasicInfos() methods)<br/><br/>
	* player_score: the current score of the player (displayed in the player panel). You must update this field to update player's scores.
	* player_score_aux: the secondary score, used as a tie breaker. You must update this field according to tie breaking rules of the game (see also: [[Main_game_logic:_yourgamename.game.php#Manage_player_scores_and_Tie_breaker\|Manage_player_scores_and_Tie_breaker]])		* <strong>player_score</strong>: the current score of the player (displayed in the player panel). You must update this field to update player's scores.
			* <strong>player_score_aux</strong>: the secondary score, used as a tie breaker. You must update this field according to tie breaking rules of the game (see also: [[Main_game_logic:_yourgamename.game.php#Manage_player_scores_and_Tie_breaker\|Manage_player_scores_and_Tie_breaker]])<br/><br/>

			* <strong>player_table_order</strong>: gives an indication of the rank of the player by order of arrival in the lobby (starting with 1). It is not the same as player_no which is the player order <u>within</u> the game. This is useful to set custom teams if wished in a game option (for instance 1st-2nd vs 3rd-4th).<br /><strong><u>CAUTION:</u></strong> This value is currently <u>not guaranted</u> to be actually equal with the rank of the player in the table. For example, in a 4 player game, if the table was full but the 3rd player have left before the game starts, the 4th player becomes 3rd on this table <u>but</u> their player_table_no is still equal to 4! If another player then joins, their player_table_no will then be 5...<br />Thus, it is essential to normalize these values first in the game setup if you wish to use them to prevent bugs at game launch. For example, if the set of player_table_order are <player A>: 3, <player B>: 2, <player C>: 5, <player D>: 7, you see that you can't read that values as ranks directly, but you can still deduce that <player B> was 1st on the table, then <player A> then <player C> then <player D> <strong>;-)</strong>

	== CREATE TABLES ==		== CREATE TABLES ==

Tutchek: Added navigation

2020-04-15T21:02:54Z

Added navigation

← Папярэдн. версія		Версія ад 23:02, 15 красавіка 2020
Радок 1:		Радок 1:
			{{Studio_Framework_Navigation}}

	In this file you specify the database schema of your game.		In this file you specify the database schema of your game.

Amadannabriona: /* CREATE TABLES */

2018-10-06T16:56:22Z

CREATE TABLES

← Папярэдн. версія		Версія ад 18:56, 6 кастрычніка 2018
Радок 49:		Радок 49:
	</pre>		</pre>

	'''Note''': if you put comments, you cannot do it in same line ~~than~~ code,		'''Note''': if you put comments, you cannot do it in the same line as code.

			Example:

	<pre>		<pre>
	`3` BOOL NOT NULL DEFAULT 1, -- activated or not		`3` BOOL NOT NULL DEFAULT 1, -- activated or not
	</pre>		</pre>

	will comment ~~also starting from~~ `3` BOOL, and code will not be ~~taken into account~~.		will also comment out `3` BOOL, and that code will not be executed.

	== Link ==		== Link ==

Nanaki404 на 16:52, 4 снежня 2016

2016-12-04T16:52:56Z

← Папярэдн. версія		Версія ад 18:52, 4 снежня 2016
Радок 61:		Радок 61:
	== Errors Log ==		== Errors Log ==
	To trace Database creation check the logs that you can access in /admin/studio.		To trace Database creation check the logs that you can access in /admin/studio.

			== Post-release database modification ==
			If you want to modify your database schema after the first release of your game in production, you should consult the [[Post-release phase#Updating the database schema\|related section]]

Een на 09:19, 26 ліпеня 2015

2015-07-26T09:19:51Z

← Папярэдн. версія		Версія ад 11:19, 26 ліпеня 2015
Радок 3:		Радок 3:
	This file contains SQL queries that will be executed during the creation of your game table.		This file contains SQL queries that will be executed during the creation of your game table.

	Note: you can't change the database schema during the game.		'''Note:''' you can't change the database schema during the game.

	== Create your schema ==		== Create your schema ==

	To build this file, we recommend you to build the tables you need with the PhpMyAdmin tool (see BGA user guide), and then to export them and to copy/paste the content inside this file.		To build this file, we recommend you to build the tables you need with the PhpMyAdmin tool (see BGA user guide), and then to export them and to copy/paste the content inside this file.

			'''Note:''' you must not use for a column the same name as for the table, as the framework replay function relies on regexp substitution to save/restore a previous state in a clone table with another name.

	== Default tables ==		== Default tables ==
Радок 58:		Радок 60:

	== Errors Log ==		== Errors Log ==
	To trace Database creation~~, you've got a small summun up in red bars during~~ the ~~game, but details are in~~ logs that you can access in /admin/studio.		To trace Database creation check the logs that you can access in /admin/studio.

Rudolf: /* CREATE TABLES */ activated

2013-03-31T13:26:02Z

CREATE TABLES: activated

← Папярэдн. версія		Версія ад 15:26, 31 сакавіка 2013
Радок 49:		Радок 49:
	'''Note''': if you put comments, you cannot do it in same line than code,		'''Note''': if you put comments, you cannot do it in same line than code,
	<pre>		<pre>
	`3` BOOL NOT NULL DEFAULT 1, --		`3` BOOL NOT NULL DEFAULT 1, -- activated or not
	</pre>		</pre>

	will comment also starting from `3` BOOL, and code will not be taken into account.		will comment also starting from `3` BOOL, and code will not be taken into account.

Rudolf: /* Default tables */

2013-03-31T13:24:39Z

Default tables

← Папярэдн. версія		Версія ад 15:24, 31 сакавіка 2013
Радок 28:		Радок 28:
	* player_score: the current score of the player (displayed in the player panel). You must update this field to update player's scores.		* player_score: the current score of the player (displayed in the player panel). You must update this field to update player's scores.
	* player_score_aux: the secondary score, used as a tie breaker. You must update this field according to tie breaking rules of the game (see also: [[Main_game_logic:_yourgamename.game.php#Manage_player_scores_and_Tie_breaker\|Manage_player_scores_and_Tie_breaker]])		* player_score_aux: the secondary score, used as a tie breaker. You must update this field according to tie breaking rules of the game (see also: [[Main_game_logic:_yourgamename.game.php#Manage_player_scores_and_Tie_breaker\|Manage_player_scores_and_Tie_breaker]])

			== CREATE TABLES ==
			you can create tables, using engine InnoDB
			<pre>
			CREATE TABLE IF NOT EXISTS `hands`
			(
			`id` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
			`player_id` TINYINT(1) NOT NULL,
			`1` BOOL NOT NULL DEFAULT 1,
			`2` BOOL NOT NULL DEFAULT 1,
			`3` BOOL NOT NULL DEFAULT 1,
			`4` BOOL NOT NULL DEFAULT 1,
			`5` BOOL NOT NULL DEFAULT 1,
			`6` BOOL NOT NULL DEFAULT 1,
			`7` BOOL NOT NULL DEFAULT 1,
			PRIMARY KEY (`id`)
			) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
			</pre>

			'''Note''': if you put comments, you cannot do it in same line than code,
			<pre>
			`3` BOOL NOT NULL DEFAULT 1, --
			</pre>
			will comment also starting from `3` BOOL, and code will not be taken into account.

			== Link ==
			You can add your Db inits in function SetupNewGame() from file 'gamename.game.php'

			== Errors Log ==
			To trace Database creation, you've got a small summun up in red bars during the game, but details are in logs that you can access in /admin/studio.