This repository has been archived by the owner on Nov 24, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 115
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Avoid large mysql packages on statbuilder
- Loading branch information
Showing
1 changed file
with
19 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ffb4350
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello what do you mean with this commit adding some limits ?
Regards
ffb4350
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have 1000 players, statbuilder collects alle data an send one big query with all data.
This update will send queries every 50 player to avoid big querys, stats works now without a the requirement of a high vaule max packet size ...
ffb4350
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes thats what i though i wanted to be sure, will be great since i reached 2.900 players registered
also last question for that one will it affect the time it takes to run or no ? i mean will it take longer then sending a big data packet ?
ffb4350
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ffb4350
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Error from cronjob:
USER ERROR: "SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax;
in : includes/classes/Database.class.php | Line: 198
Stack trace:
#0 /includes/classes/Database.class.php(198): PDO->query('INSERT INTO un...')
#1 /includes/classes/class.statbuilder.php(158): Database->nativeQuery('INSERT INTO %%...')
#2 /includes/classes/class.statbuilder.php(400): statbuilder->SaveDataIntoDB('INSERT INTO %%...')
#3 /includes/classes/cronjob/StatisticCronjob.class.php(38): statbuilder->MakeStats()
#4 /includes/classes/Cronjob.class.php(68): StatisticCronjob->run()
#5 /cronjob.php(65): Cronjob::execute(2)
Error from manual update:
USER ERROR: "SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax;
in: includes/classes/Database.class.php | Line: 198
Stack trace:
#0 /includes/classes/Database.class.php(198): PDO->query('INSERT INTO un...')
#1 /includes/classes/class.statbuilder.php(158): Database->nativeQuery('INSERT INTO %%...')
#2 /includes/classes/class.statbuilder.php(400): statbuilder->SaveDataIntoDB('INSERT INTO %%...')
#3 /includes/pages/adm/ShowStatUpdatePage.php(35): statbuilder->MakeStats()
#4 /admin.php(154): ShowStatUpdatePage()
ffb4350
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i had the same problem jan...
Regards