[4ever16]

I have a wierd problem in my head i know the solution but something is not adding upp.

Code.

PHP Code:

 formatex( szQuery, 3799, "REPLACE INTO `today` (`player_id2`, `player_name2`, `kills2`, `deaths2`, `points2`) VALUES ('%s', '%s', '%d', '%d', '%d');", steam, GetSecureName(Name), pTempKills[id], pTempDeaths[id], pTempPoints[id]); "ON DUPLICATE KEY UPDATE `text1` = VALUES ('player_id2');", steam; 


So basicly this code works. It creates if it doesnt exists. It also updates to new values.

BUT.

When CS 1.6 map restarts values starts from 0 so basicly it deletes old values and adds new values.

I want to REPLACE values without DELETING values.
I checked the plugin .SMA and i don't see anything wrong there.

I don't understand why it DELETES and RESTARTS VALUE COUNT when map change is made or when plugin is restarted?!

How can i REPLACE BUT NEVER DELETE OLD VALUES? Thanks!

[4ever16]

I feel like i need to use DUPLICATE or something.

Can someone help me out in someway cause im not thinking "right" right now.

[jimaway]

use INSERT not REPLACE

[Bugsy]

INSERT will always add a new record so you will end up with dupes.

Ideally, you should use INSERT for a new player, and UPDATE for an existing player.

REPLACE INTO essentially covers both without the need to know whether a record already exists. But, to use it correctly, you need to take the PRIMARY KEY or UNIQUE index into consideration.

[fysiks]

INSERT should fail if the column is configured as unique and the data for that column already exists.

If you don't know that a key will exist and you want to create if it doesn't, you can use INSERT INTO ... ON DUPLICATE KEY UPDATE ... I use this to increment a counter. If it doesn't exist, it inserts a 1, if it already exists, it increments the value all in a single MySQL instruction.

[Bugsy]

Here's an example:

CREATE TABLE `tblPlayers` ( `ID` INTEGER PRIMARY KEY AUTOINCREMENT, `SteamID` TEXT NOT NULL UNIQUE, `PlayerName` TEXT, `Kills` INTEGER )

REPLACE INTO tblPlayers (SteamID, PlayerName, Kills) VALUES ("STEAM_123","bugsy",5);
REPLACE INTO tblPlayers (SteamID, PlayerName, Kills) VALUES ("STEAM_123","bugsy123",25);
REPLACE INTO tblPlayers (SteamID, PlayerName, Kills) VALUES ("STEAM_123","bugsy456",31);

With each execution, it results in only 1 record for the player with a SteamID of 'STEAM_123', updating only the player name and kills value. Primary key ID changes, but that doesn't matter since it's just an autoincrementing ID.