Deez Nutz

if gd2 is retired then BBOS should be officially closed. and, if it will not load all games there is no time to fix it anymore unless someone else would like to take over. however, I still see data https://gd2.mlb.com/components/game/mlb/year_2019/month_09/day_28/gid_2019_09_28_atlmlb_nynmlb_1/inning/inning_1.xml remember that if you navigate to https://gd2.mlb.com/components/game/mlb/year_2019/month_09/day_28 you will get data but this, with the / at the end, will not https://gd2.mlb.com/components/game/mlb/year_2019/month_09/day_28/...

6.7.1

Ok, all the issues I could find with uploading 2019 have been fixed as well as anything I could find that erred for 2018. 2018 has games that are missing the game_pk also. Mostly spring games. Those should now load as well if you grab version 6.7.1. There was also an issue that Python's urllib class starting taking forwever to download a single files. I had to swap out the use of that library for urllib2. This seems to work but I have only run it against 2019 and 18 as mentioned. Let me know if you...

I did get the same error on 2019. no timeline to fix it though. April I hope...? On Wed, Mar 13, 2019 at 7:34 AM Addison addy@users.sourceforge.net wrote: same error for me. also, the 2007 and earlier games seem to have an issue with the park attributes which prevents loading any games at all. i've dug into the code a bit but still cannot resolve - has anyone else been successful fixing this bug? Attachments: bbos_gamepk_error.PNG https://sourceforge.net/p/baseballonastic/discussion/820145/thread/3005a7284e/f9dd/attachment/bbos_gamepk_error.PNG...

I do plan on loading data from 2019 in the coming weeks but I have not yet. I'll see if i get an error at that time also On Sun, Mar 3, 2019 at 9:37 PM Mark O'L phunpolo@users.sourceforge.net wrote: Hi folks, Seeing the following error while trying to load 2019 games. Is anyone else dealing with this? ERROR 2019-03-03 23:18:16,392 Thread-6 bbos.consume.83 Died with Exception: Exception in thread Thread-6: Traceback (most recent call last): File "C:\Python27\lib\threading.py", line 801, in bootstrap_inner...

it is hard using the gameday data as is. it will also include spring and post season if you loaded those games. but i believe what you have is the general idea. this is why the "normalize" sql script is there. it makes nice relational tables out of the data. you could try running that and then query the "mlb" schema it creates. it basically makes a whole new nicer database and cleans up lots of junk data. if you want to use the gameday schema as is then the sql in the normalize.sql can help you see...

each db statement relies on the previous succeeding. so what is the first statement that throws an actual error (non-group by/table does not exist) and what is that error? also watch out for those lines that say 0 rows effected. that could mean a query that is supposed to find some data didn't and that the gameday data didn't actually all load On Mon, May 21, 2018 at 12:22 AM, Steven J Tighe resumeman@users.sourceforge.net wrote: So for the record I found the "group by" error - the server was set...

i think your best bet it to run it by hand. you can make it work but it requires changing coding. the table does not exist error is normal, because it deletes each table and then creates it. so if the script has yet to work it will always give those errors. i think you want to look for the errors it is giving that are not "table doesn't exist" cause if you only have two tables then it went wrong at some point. you could also pick apart the file and run one part at a time to make sure each part works...