StatsLab SQL Utilities for OOTPX

[Stu]

Originally Posted by Stu

Also I'm still getting strange permission issues. All folders are currently set to 755 but anytime it needs to write a file I get an error. As an example, I get this when trying to view a players game logs:

If I set the permissions to 777 it works but I obviously don't want to leave them at 777. Is there something wrong in my configuration that would be causing this?

In case anybody else experiences this issue, it was because my web server runs under a user account that didn't have write access to any of the folders on my site. I fixed it by simply changing ownership of the ootpsqlou folder and sqldump folder to the user that runs the web server.

Originally Posted by Stu

For anybody who is interested I was able to run the season metrics for all but the first 3 years of my league. I had all my old backups so just imported the backup from before the World Series of each year as if it was an OOTP 9 league. This worked for league files from OOTP 2007, 8 and 9.

I wasn't able to import the first 3 seasons because I can't find the backups.

I was also able to run the season metrics for years where I didn't have data. It needs the park factor data to be set so I set the park factors for the first 3 years equal to the average of the years I did have the data.

Once the park factors table was populated I manually edited the season metrics file to change the $year variable to the year I wanted to run it. This seemed to work fine. Not an exact science since the park factors aren't 100% accurate but it's close enough.

[dangarion]

Well it looks like my use of StatsLab is over. I merged my DBs together with my host and the new server that I'm on doesn't allow the large DB imports I was previously doing. I tried doing the splitting files thing once, but I don't have an hour to mess around doing that by hand.

My host suggesting doing the import via shell... If I import the SQL files via shell is it going to work? I haven't looking into what exactly the statslab script does when it imports, does it parse information or does it just import?

[snnort]

When you say "doesn't allow the large DB imports" are you implying that you can not upload the 61 or so individual SQL files that OOTP dumps? OR that once uploaded, your failing when attempting to press the "Load SQL files" button?

What host do you use?

[dangarion]

Originally Posted by snnort

When you say "doesn't allow the large DB imports" are you implying that you can not upload the 61 or so individual files? OR that once uploaded, your failing when attempting to press the "Load SQL files" button?

What host do you use?

It's actually 30 or 31 files if I remember correctly. I've been running StatsLab for about 3 or 4 months, but my host no longer allows DB imports of more then 7 MB via web the web based interface.. Thought me saying saying something about splitting the files would explained I'm having a problem with the size of the files, especially since I've never heard of a host blocking multiple files.

[BMW]

dangarion,
I've had that problem for ages. It's such a pain. Make some noise on the post here, where I ask Markus to put in something to automatically break up the files:
Break up very large MySQL files

[fhomess]

Originally Posted by dangarion

My host suggesting doing the import via shell... If I import the SQL files via shell is it going to work? I haven't looking into what exactly the statslab script does when it imports, does it parse information or does it just import?

The import handles some things:
1. Translates special characters in player names into a readable character set.
2. Fixes some issues with fields left blank in specific SQL files (e.g. leagues.mysql.sql is missing the last two fields)
3. Updates the StatsLab user table based on the human_managers table out of OOTP.
4. The next StatsLab patch will do some indexing on the tables that Markus doesn't include.

[dangarion]

Originally Posted by fhomess

The import handles some things:
1. Translates special characters in player names into a readable character set.
2. Fixes some issues with fields left blank in specific SQL files (e.g. leagues.mysql.sql is missing the last two fields)
3. Updates the StatsLab user table based on the human_managers table out of OOTP.
4. The next StatsLab patch will do some indexing on the tables that Markus doesn't include.

Ouch, ok, looks like plan B (use someone elses host for StatsLab).

[fhomess]

Originally Posted by dangarion

Well it looks like my use of StatsLab is over. I merged my DBs together with my host and the new server that I'm on doesn't allow the large DB imports I was previously doing. I tried doing the splitting files thing once, but I don't have an hour to mess around doing that by hand.

What if you, hypothetically had a button to split all SQL files over X size, and then another button that would do the import of all the files after that, using the split files instead. Would that resolve the issue?

[dangarion]

Originally Posted by fhomess

What if you, hypothetically had a button to split all SQL files over X size, and then another button that would do the import of all the files after that, using the split files instead. Would that resolve the issue?

If it would automatically split all the large files (instead of the current way where I have to do them each by hand), and then automatically imported them all that would be better.

[Recte44]

I still can't change the Draft Order and make it stick. Is there some permissions thing I need to change to make this work, and if so, what is it???

[fhomess]

Originally Posted by dangarion

If it would automatically split all the large files (instead of the current way where I have to do them each by hand), and then automatically imported them all that would be better.

Originally Posted by Recte44

I still can't change the Draft Order and make it stick. Is there some permissions thing I need to change to make this work, and if so, what is it???

PM's sent to both of you.

[snnort]

you are the man, fhomess.

[BMW]

You might run into a limit to where PHP can read large files if you use fopen() and fread().

I originally couldn't import a MySQL file that was over 16MB.

Splitting the files fixed that, until PHP wasn't able to split a file over 70MB, because it wasn't capable in opening it. It was exceeding the memory limit.

So I've had to forgo the at_bats file since using OOTP, as it can grow to that size very fast.

If you have a different solution, let me know.

[Recte44]

Frank-

Using the Draft Utility now (thanks for fixing it, btw!!) but ran into a new problem....

After the first auto-pick the utility is now randomly auto-picking people! Any ideas?

[fhomess]

Originally Posted by Recte44

Frank-

Using the Draft Utility now (thanks for fixing it, btw!!) but ran into a new problem....

After the first auto-pick the utility is now randomly auto-picking people! Any ideas?

PM Sent.

[Recte44]

Frank,

New/old issue.

Started a new year. Last Sim won't update. Still has last years playoffs boxscores.

[fhomess]

Originally Posted by Recte44

Frank,

New/old issue.

Started a new year. Last Sim won't update. Still has last years playoffs boxscores.

Make sure the ootpsqlou/cache directory gets cleared when you update your SQL files. The util should do this automatically when you load your SQL files provided the permissions are there to do so.

Patch 2 will have the ability to turn off the caching functionality.

[Recte44]

Still not working even after I manually cleared out the cache folder. It's June of 1971 now and Last Sim is still from the 1970 playoffs.

[fhomess]

Originally Posted by Recte44

Still not working even after I manually cleared out the cache folder. It's June of 1971 now and Last Sim is still from the 1970 playoffs.

There are 3 possible causes of old data showing up in the util:
1. The files are still in your ootpsqlou/cache folder.
2. Your SQL database didn't get updated.
3. The web page is cached in your browser.

[fhomess]

Patch #2 has been released for use with OOTPX 10.4. Please do not use this patch until you upgrade to 10.4 (to be released later today). If you're using the development tracker, you'll want to use this patch as soon as you upgrade as there are some changes to how ratings are listed in the SQL dump.

Cheers!