If you are developing a Python application that needs access to the
MusicBrainz
data, you can use
the mbdata.models
module to get
SQLAlchemy models mapped to the
MusicBrainz database tables.
All tables from the MusicBrainz database are mapped, all foreign keys have one-way relationships set up and some models, where it's essential to access their related models, have two-way relationships (collections) set up.
In order to work with the relationships efficiently, you should use the appropriate kind of eager loading.
Example usage of the models:
>>> from sqlalchemy import create_engine
>>> from sqlalchemy.orm import sessionmaker
>>> from mbdata.models import Artist
>>> engine = create_engine('postgresql://musicbrainz:[email protected]/musicbrainz', echo=True)
>>> Session = sessionmaker(bind=engine)
>>> session = Session()
>>> artist = session.query(Artist).filter_by(gid='8970d868-0723-483b-a75b-51088913d3d4').first()
>>> print artist.name
If you use the models in your own application and want to define foreign
keys from your own models to the MusicBrainz schema, you will need to
let mbdata
know which metadata object to add the MusicBrainz tables
to:
from sqlalchemy.ext.declarative import declarative_base
Base = declarative_base()
# this should be the first place where you import anything from mbdata
import mbdata.config
mbdata.config.configure(base_class=Base)
# now you can import and use the mbdata models
import mbdata.models
You can also use mbdata.config
to re-map the MusicBrainz schema
names, if your database doesn't follow the original structure:
import mbdata.config
mbdata.config.configure(schema='my_own_mb_schema')
If you need sample MusicBrainz data for your tests, you can use
mbdata.sample_data
:
from mbdata.sample_data import create_sample_data
create_sample_data(session)
Normally you should work against a regular PostgreSQL database with MusicBrainz data, but for testing purposes, you can use a SQLite database with small data sub-set used in unit tests. You can create the database using:
./bin/create_sample_db.py sample.db
Then you can change your configuration:
DATABASE_URI = 'sqlite:///sample.db'
Running tests:
pytest -v
If you want to see the SQL queries from a failed test, you can use the following:
MBDATA_DATABASE_ECHO=1 pytest -v
Jenkins task that automatically runs the tests after each commit is here.