Subpage under development, new version coming soon!
Subject: New NTDB Database
Nevermind, server error came because of using Safari (Apple's browser) in stead of FireFox
age update = ok now :)
age update = ok now :)
any reason why the age update doesn't work entirely as it should? Works for most cases but there are players it just doesn't update age for.
they are deleted in sokker? The script should now move them to the archive aka the delete bin
those ones were fine. We had a couple that didn't age that still existed (albeit they are in the archive, but other archive players updated properly).
for the past 3 weeks now iv been getting that server error thing, when updating form...
tried again there now and still not working :/
tried again, and this happened
Please, don't close this window before the update is finished
Player Jake Callan with id of 12439984 has been deleted from sokker database
The form and other public info of all active players were successfully updated
it doesnt scroll through them individually anymore, or is it just not working for me?
EDIT: well form is right, so im assuming it did update right, unless Nin did it already today...
(edited)
tried again there now and still not working :/
tried again, and this happened
Please, don't close this window before the update is finished
Player Jake Callan with id of 12439984 has been deleted from sokker database
The form and other public info of all active players were successfully updated
it doesnt scroll through them individually anymore, or is it just not working for me?
EDIT: well form is right, so im assuming it did update right, unless Nin did it already today...
(edited)
The thing about errors on the page is due to the browser timeout. Since we migrated to MySQL 5, the script stopped the flush process and all browsers think the page have errors and kill it.
If one try to update just a small group of players, it works nicely.
And why after some attempt, only a few players appear in the list? Because the script update player by player and it is done until the browser closes the connexion. Even with the error message, some players were updated. When the players missing group is small enough, then the process is not killed and the page show correctly.
@mohamed14: about your country, just ask your coach to contact me.
If one try to update just a small group of players, it works nicely.
And why after some attempt, only a few players appear in the list? Because the script update player by player and it is done until the browser closes the connexion. Even with the error message, some players were updated. When the players missing group is small enough, then the process is not killed and the page show correctly.
@mohamed14: about your country, just ask your coach to contact me.
hi i have a problem with NTDB database
when i click on a flag i see this message
Table 'ntdbpops_temp' already exists
so i can't update players
i have already download new exsokker and firesokker and i update firefox
(edited)
when i click on a flag i see this message
Table 'ntdbpops_temp' already exists
so i can't update players
i have already download new exsokker and firesokker and i update firefox
(edited)
same.. i tried updating a player earlier and got it too... wasnt sure if it was a firesokker or NTDB problem.. since firesokker hasnt been updated or anything though i guess it is NTDB error...
Hi people,
Could someone try it now? I'm without access to DW nor FireSokker.
@rtg: could you take a look on it please? After a player is updated, he is also sent to the ntdbpops table (source to graphs). But if a player is updated twice in a day, we have a duplicated row.
To avoid it, the script run a select DISTINCT on this table and save it as ntdbpops_temp. Finally, the new table replaces the old one replacing it. I think two good solutions would be:
- create a trigger in order to do this job;
- run a select before inserting a new record to ntdbpops to avoid duplicates;
Today was second time we had the same problem and I'm worried it will not stop with the manual table drop.
Could someone try it now? I'm without access to DW nor FireSokker.
@rtg: could you take a look on it please? After a player is updated, he is also sent to the ntdbpops table (source to graphs). But if a player is updated twice in a day, we have a duplicated row.
To avoid it, the script run a select DISTINCT on this table and save it as ntdbpops_temp. Finally, the new table replaces the old one replacing it. I think two good solutions would be:
- create a trigger in order to do this job;
- run a select before inserting a new record to ntdbpops to avoid duplicates;
Today was second time we had the same problem and I'm worried it will not stop with the manual table drop.
Invalid password - what am I doing wrong?
(edited)
(edited)
maybe caps lock or something.. or someone got ur pass... am guessing its wrong anyways :P