ExecuteSQLUpdate - Revision history

ThePiotrek at 14:19, 9 October 2016

2016-10-09T14:19:09Z

← Older revision		Revision as of 14:19, 9 October 2016
Line 9:		Line 9:
	The executed SQL query is the following:		The executed SQL query is the following:

	<syntaxhighlight lang="lua">~~[sql]~~UPDATE <table> SET <set> WHERE <conditions></syntaxhighlight>		<syntaxhighlight lang="lua">UPDATE <table> SET <set> WHERE <conditions></syntaxhighlight>

	==Syntax==		==Syntax==

AlexTMjugador: Changed "DeprecatedWithAlt" template to "Deprecated"

2015-02-13T16:21:01Z

Changed "DeprecatedWithAlt" template to "Deprecated"

← Older revision		Revision as of 16:21, 13 February 2015
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{Server function}}		{{Server function}}
	{{~~DeprecatedWithAlt~~\|executeSQLQuery\|See the examples at executeSQLQuery for equivalent UPDATE usage}}		{{Deprecated\|executeSQLQuery\|See the examples at executeSQLQuery for equivalent UPDATE usage.}}

	This function updates one or more rows in the database, by using the set parameter and conditions to change field values in specific rows.		This function updates one or more rows in the database, by using the set parameter and conditions to change field values in specific rows.

Ccw at 21:21, 20 July 2012

2012-07-20T21:21:42Z

← Older revision		Revision as of 21:21, 20 July 2012
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{Server function}}		{{Server function}}
			{{DeprecatedWithAlt\|executeSQLQuery\|See the examples at executeSQLQuery for equivalent UPDATE usage}}
	This function updates one or more rows in the database, by using the set parameter and conditions to change field values in specific rows.		This function updates one or more rows in the database, by using the set parameter and conditions to change field values in specific rows.

Awwu: /* Example */

2009-08-27T12:20:59Z

Example

← Older revision		Revision as of 12:20, 27 August 2009
Line 35:		Line 35:

	function addInfoToSQL( theSpawnpoint, theTeam )		function addInfoToSQL( theSpawnpoint, theTeam )
	sourcename = ~~getClientName~~ ( source ) -- get the player's name		sourcename = getPlayerName ( source ) -- get the player's name

	-- try to retrieve the player data from the db		-- try to retrieve the player data from the db
Line 55:		Line 55:
	addEventHandler ( "onPlayerSpawn", getRootElement(), addInfoToSQL )		addEventHandler ( "onPlayerSpawn", getRootElement(), addInfoToSQL )
	</syntaxhighlight>		</syntaxhighlight>


	==See Also==		==See Also==
	{{Registry_functions}}		{{Registry_functions}}

Talidan at 14:56, 26 August 2007

2007-08-26T14:56:05Z

← Older revision		Revision as of 14:56, 26 August 2007
Line 26:		Line 26:

	==Example==		==Example==
			This example creates a SQL table when a map loads, and stores info about a player to that database when he spawns.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function onMapLoad ()		function onMapLoad ()
Line 33:		Line 34:
	addEventHandler ( "onGamemodeMapStart", getRootElement(), onMapLoad )		addEventHandler ( "onGamemodeMapStart", getRootElement(), onMapLoad )

	function ~~onPlayerSpawn~~ ( ~~spawnpoint~~, ~~team~~ )		function addInfoToSQL( theSpawnpoint, theTeam )
	sourcename = getClientName ( source ) -- get the player's name		sourcename = getClientName ( source ) -- get the player's name

Line 52:		Line 53:
	outputChatBox ( "Your head model is " .. result[1][2] )		outputChatBox ( "Your head model is " .. result[1][2] )
	end		end
	addEventHandler ( "onPlayerSpawn", getRootElement(), ~~onPlayerSpawn~~ )		addEventHandler ( "onPlayerSpawn", getRootElement(), addInfoToSQL )
	</syntaxhighlight>		</syntaxhighlight>


	==See Also==		==See Also==
	{{Registry_functions}}		{{Registry_functions}}

Arc at 12:33, 21 August 2007

2007-08-21T12:33:36Z

← Older revision		Revision as of 12:33, 21 August 2007
Line 11:		Line 11:
	==Syntax==		==Syntax==
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	bool executeSQLUpdate ( string ~~table~~, string set, [ string conditions ] )		bool executeSQLUpdate ( string tableName, string set, [ string conditions ] )
	</syntaxhighlight>		</syntaxhighlight>

	===Required Arguments===		===Required Arguments===
	*'''~~table~~:''' The name of the table you want to modify.		*'''tableName:''' The name of the table you want to modify.
	*'''set:''' The query you want to execute on that table. The default SQL syntax is used, which means that the = is used to set a value and the ' is used to specify a value (e.g. ''test = 'hi' ''). The , is used as a delimiter for multiple queries.		*'''set:''' The query you want to execute on that table. The default SQL syntax is used, which means that the = is used to set a value and the ' is used to specify a value (e.g. ''test = 'hi' ''). The , is used as a delimiter for multiple queries.

Line 22:		Line 22:

	===Returns===		===Returns===
	The function returns ~~a ''boolean'' which is~~ ''true'' on success, and ''false'' on failure.		The function returns ''true'' on success, and ''false'' on failure.


Line 31:		Line 31:
	executeSQLCreateTable ( "players", "clothes_head_texture TEXT, clothes_head_model TEXT, player TEXT" )		executeSQLCreateTable ( "players", "clothes_head_texture TEXT, clothes_head_model TEXT, player TEXT" )
	end		end
			addEventHandler ( "onGamemodeMapStart", getRootElement(), onMapLoad )

	function onPlayerSpawn ( spawnpoint, team )		function onPlayerSpawn ( spawnpoint, team )
Line 47:		Line 48:

	-- get the clothes data for the player		-- get the clothes data for the player
	result = executeSQLSelect ( "players", "clothes_head_texture, clothes_head_model", "player = '" .. sourcename .. "'" )		result = executeSQLSelect ( "players", "clothes_head_texture, clothes_head_model", "player = '" .. sourcename .. "'" )
	outputChatBox ( "Your head texture is " .. result[1][1] )		outputChatBox ( "Your head texture is " .. result[1][1] )
	outputChatBox ( "Your head model is " .. result[1][2] )		outputChatBox ( "Your head model is " .. result[1][2] )
	end		end
			addEventHandler ( "onPlayerSpawn", getRootElement(), onPlayerSpawn )
	</syntaxhighlight>		</syntaxhighlight>

	==See Also==		==See Also==
	{{Registry_functions}}		{{Registry_functions}}

Erorr404 at 01:46, 5 August 2007

2007-08-05T01:46:07Z

← Older revision		Revision as of 01:46, 5 August 2007
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
			{{Server function}}
	This function updates one or more rows in the database, by using the set parameter and conditions to change field values in specific rows.		This function updates one or more rows in the database, by using the set parameter and conditions to change field values in specific rows.

IJs at 15:28, 23 September 2006

2006-09-23T15:28:29Z

← Older revision		Revision as of 15:28, 23 September 2006
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	This function updates one or more rows in the database.		This function updates one or more rows in the database, by using the set parameter and conditions to change field values in specific rows.
	~~This function sets one or more rows in the registry. Since the registry is powered~~ by ~~a SQLite database, this function automatically executes an ''UPDATE'' query with~~ the ~~appropriate parameters~~.

	The SQLite database contains globally stored data and can be used by scripts to store and retrieve data in a structured manner.		The SQLite database contains globally stored data and can be used by scripts to store and retrieve data in a structured manner.

IJs at 15:27, 23 September 2006

2006-09-23T15:27:12Z

← Older revision		Revision as of 15:27, 23 September 2006
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
			This function updates one or more rows in the database.
	This function sets one or more rows in the registry. Since the registry is powered by a SQLite database, this function automatically executes an ''UPDATE'' query with the appropriate parameters.		This function sets one or more rows in the registry. Since the registry is powered by a SQLite database, this function automatically executes an ''UPDATE'' query with the appropriate parameters.

	The ~~registry is~~ stored ~~globally~~ and can be ~~read from and written to~~ by ~~all~~ scripts ~~in sessions. This is useful if you want~~ to store data ~~for your script~~.		The SQLite database contains globally stored data and can be used by scripts to store and retrieve data in a structured manner.

	The ~~actual~~ SQL query ~~that~~ is ~~executed will be~~ the following:		The executed SQL query is the following:

	<~~pre~~>UPDATE <table> SET <set> WHERE <conditions></~~pre~~>		<syntaxhighlight lang="lua">[sql]UPDATE <table> SET <set> WHERE <conditions></syntaxhighlight>

	==Syntax==		==Syntax==
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	bool ~~setRegistryQuery~~ ( string table, string set, [ string conditions ] )		bool executeSQLUpdate ( string table, string set, [ string conditions ] )
	</syntaxhighlight>		</syntaxhighlight>

	===Required Arguments===		===Required Arguments===
	*'''table:''' The table you want to modify.		*'''table:''' The name of the table you want to modify.
	*'''set:''' The query you want to execute on that table. The default SQL syntax is used, which means that the = is used to set a value and the ' is used to specify a value (e.g. ''test = 'hi' ''). The , is used as a delimiter for multiple queries.		*'''set:''' The query you want to execute on that table. The default SQL syntax is used, which means that the = is used to set a value and the ' is used to specify a value (e.g. ''test = 'hi' ''). The , is used as a delimiter for multiple queries.

Line 22:		Line 23:
	===Returns===		===Returns===
	The function returns a ''boolean'' which is ''true'' on success, and ''false'' on failure.		The function returns a ''boolean'' which is ''true'' on success, and ''false'' on failure.


			==Example==
			<syntaxhighlight lang="lua">
			function onMapLoad ()
			-- create our table, if it doesn't already exist
			executeSQLCreateTable ( "players", "clothes_head_texture TEXT, clothes_head_model TEXT, player TEXT" )
			end

			function onPlayerSpawn ( spawnpoint, team )
			sourcename = getClientName ( source ) -- get the player's name

			-- try to retrieve the player data from the db
			result = executeSQLSelect ( "players", "player", "player = '" .. sourcename .. "'" )
			if ( result == false ) then -- see if any data was found at all
			outputChatBox ( "This is your first time here! Welcome " .. sourcename .. "!", source )
			executeSQLInsert ( "players", "'none', 'none', '" .. sourcename .. "'" )
			else
			outputChatBox ( "Welcome back " .. sourcename .. "!", source )
			executeSQLUpdate ( "players", "clothes_head_texture = 'hairgreen', clothes_head_model = 'somehead'",
			"player = '" .. sourcename .. "'" )
			end

			-- get the clothes data for the player
			result = executeSQLSelect ( "players", "clothes_head_texture, clothes_head_model", "player = '" .. sourcename .. "'" )
			outputChatBox ( "Your head texture is " .. result[1][1] )
			outputChatBox ( "Your head model is " .. result[1][2] )
			end
			</syntaxhighlight>

	==See Also==		==See Also==
	{{Registry_functions}}		{{Registry_functions}}

IJs: SetRegistryQuery moved to ExecuteSQLUpdate

2006-09-23T15:06:28Z

SetRegistryQuery moved to ExecuteSQLUpdate

← Older revision

Revision as of 15:06, 23 September 2006