[Crayder]

Quote:

Originally Posted by Gammix What i meant was sort of similar to this logic. Example: Code: SavePVar(playerid, "Test"); // The execute interval has started // New variables added (query isn't executed) SavePVar(playerid, "Test2"); SavePVar(playerid, "Test3"); SavePVar(playerid, "Test4"); // After 'X' seconds (say 2 secs), the query is executed and result is free! (similar with loading functions)

The problem with this is things can go wrong, like what if that player disconnected within those 2 seconds? Or what if the server crashed? Or anything else that causes interruptions.

Giving the users the ability to run transactions would solve this.

Code:

//Single Query
SavePVar(playerid, "Test0");

//Multiple Queries
StartPVarQuery(); // Macro for db_query("BEGIN")
SavePVar(playerid, "Test");
SavePVar(playerid, "Test2");
SavePVar(playerid, "Test3");
SavePVar(playerid, "Test4");
EndPVarQuery(); // Macro for db_query("COMMIT")

Also, transactions are super quick, so this would speed up a lot of things. Transactions can run extreme amounts of queries in a single swoop in a very small amount of time.