…and I’ve downloaded BOS onto my Mac and I’ve gone ahead and downloaded Python 2.5.2 as well. I have followed along with Sky’s tutorial and I’m running MAMP and Sequel Pro.

With BOS downloaded, I got very excited. I could see the light. Since I have little to no idea what I’m doing from here, I opened up the Install.txt file located in the bos/doc directory. Looks like there are some useful directions here but they are for the Windows platform.

I have a few questions:

- Do I need to download and install mySQLdb for Python 2.5 if I already have Sequel Pro and MAMP running? Furthermore, it says I can run another mySQL server if I’m not running on Windows (which I’m not) so I figure that is what MAMP is for, correct?

- How do I

Prepare the database to hold game information by running \BBOS\bin\install.bat

Basically, I need a translator who can speak Mac-anese or understands the nuts and bolts to point me in the right direction. It seems as if I’m really really close. Colin, what do you think?

You should be able to talk to MySQL directly, to wit:

/Users/caledonia> ls -l retrosheet.sql.gz
-rw-r—r— 1 caledonia admin 416527259 17 Sep 17:51 retrosheet.sql.gz

/Users/caledonia> gunzip retrosheet.sql.gz
/Users/caledonia> ls -l retrosheet.sql
-rw-r—r— 1 caledonia admin 4927743578 17 Sep 17:51 retrosheet.sql

/Users/caledonia> /usr/local/mysql/bin/mysql -uroot -p
Enter password: ************

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 8
Server version: 5.1.38-log Source distribution

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.

mysql> SHOW DATABASES;
-————————-
| Database |
-————————-
| information_schema |
| mysql |
| pbp |
| test |
-————————-
4 rows in set (0.42 sec)

mysql> CREATE DATABASE retrosheet;
Query OK, 1 row affected (0.13 sec)

mysql> USE retrosheet
Database changed

mysql> SOURCE /Users/caledonia/retrosheet.sql;
Query OK, 0 rows affected (0.02 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.09 sec)
Query OK, 0 rows affected (0.03 sec)
Query OK, 0 rows affected (0.03 sec)
Query OK, 0 rows affected (0.01 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.02 sec)
Query OK, 0 rows affected (0.16 sec)
Query OK, 0 rows affected (0.01 sec)
Query OK, 0 rows affected (0.02 sec)
Query OK, 1818 rows affected (2.11 sec)
Records: 1818 Duplicates: 0 Warnings: 0

Query OK, 1820 rows affected (1.81 sec)
Records: 1820 Duplicates: 0 Warnings: 0

[Four hours later…]

Query OK, 1321 rows affected (0.09 sec)
Records: 1321 Duplicates: 0 Warnings: 0

Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.06 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.01 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)

mysql> SHOW TABLES;
-—————————————
| Tables_in_retrosheet |
-—————————————
| events |
| games |
| id |
| lkup_cd_bases |
| lkup_cd_battedball |
| lkup_cd_event |
| lkup_cd_fld |
| lkup_cd_h |
| lkup_cd_hand |
| lkup_cd_park_daynight |
| lkup_cd_park_field |
| lkup_cd_park_precip |
| lkup_cd_park_sky |
| lkup_cd_park_wind_direction |
| lkup_cd_recorder_method |
| lkup_cd_recorder_pitches |
| lkup_id_base |
| lkup_id_home |
| lkup_id_last |
| parkcode |
| rosters |
| teams |
-—————————————
22 rows in set (0.12 sec)

mysql> SELECT * FROM teams;
-———————--—————————--—————-
| YEAR_ID | TEAM_ID | LG_ID | LOC_TEAM_TX | NAME_TEAM_TX |
-———————--—————————--—————-
| 1911 | BOS | A | Boston | Red |
| 1911 | CHA | A | Chicago | White |
| 1911 | CLE | A | Cleveland | Indians |
| 1911 | DET | A | Detroit | Tigers |
| 1911 | NYA | A | New York | Highlanders |
| 1911 | PHA | A | Philadelphia | Athletics |

[Etc.]

1321 rows in set (0.10 sec)

It wouldn’t surprise me if there were a much better way to go about this, but it did work. I presume that from this point there’s a way to make Sequel Pro aware of the new database.