MMOLDB is a publicly queryable SQL database for MMOLB games inspired by the Blaseball datablase. It's still in early development.
You can connect to the MMOLDB database using any Postgresql query tool (pgAdmin is a popular choice). Connect using these settings:
mmoldb.beiju.me
. Do not add http
or https — the connection uses a different protocol.
42416
mmoldb
guest
moldybees
All other settings you should be able to leave at their defaults.
To connect using pgAdmin, go to the Query Tool Workspace (the second icon down at the very left of the screen) and input these connection settings.
Note: MMOLDB already has a *lot* of data, and as I'm writing this it's only season 2. For your sake and my server's, I suggest using low `limit`s on your queries as you're debugging them. It'll make your results load faster and reduce the load on the server. Just don't forget to take it off before getting your final results.
Contributors (project lifetime): WoofyJack, Ifhbiff, Centritide.
data.player_report_attributes
and replace it with
data.player_report_versions
and data.player_report_attribute_versions
.
These use the same valid_from
and valid_until
system that other
_versions
tables do, reflecting the fact that player reports are now
live-updating. This also adds recording of clubhouse talk quotes, which were
previously not in the database.data.games
for info.data.modifications
data.player_versions
data.player_modification_versions
data.player_equipment_versions
data.player_equipment_effect_versions
data.player_feed_versions
data.player_attribute_augments
data.player_recompositions
data.player_paradigm_shifts
data.player_report_attributes
data.games
.data.events
, but we
plan to move to storing them in a child table like Weather.Known issues:
hit_base
for home runs being Third
for some reasonstrikes_before
columntaxa.base
column bases_achieved
from bigint to int again? I swear
I did that in the last big update.abbreviation
to taxa.pitch_type
.taxa.hit_type
. Changed data.events
column hit_type
to reference taxa.base
instead and renamed it to hit_base
.taxa.base
column bases_achieved
from bigint to int. It never
should have been a bigint in the first place.taxa
, data
, and info
schemata.home_team_id
and away_team_id
to home_team_mmolb_id
and away_team_mmolb_id
in data.games
.count_strikes
and count_balls
, which used to store the
count after the event finished, which also means that it stored 0-0 for every
PA-ending event.strikes_before
and balls_before
, which store the count at the
beginning of the event. The count at the end of the event can be easily
computed, and examples are included in the documentation.away_*
and home_*
fields to put away first.