In my personal opinion (however I am new to databases as well), I would look to store the relative URL, which would be the VARCHAR from here you could store the relative path to the file (from where the script is being called from) and load the file that way.
However it may be worth writing the SQL for your tables as well. Just in case you need to alter or tweak your table structure in the beginning it makes it simpler to alter. so it would look something like this:
create database music;
use music;
create table tbl_album(
album_id int(5) not null auto_increment,
album_name varchar(50) not null,
album_artist varchar(50) not null,
album_genre varchar(50),
ablum_year varchar(4),
primary key(album_id)
);
create table tbl_tracks(
track_id int(5) not null auto_increment,
track_number int(2),
track_name varchar(50) not null,
album_id int(5),
track_url varchar(100) not null,
primary key(track_id),
foreign key (album_id) references tbl_album(album_id)
);
PS: If you do choose to write the SQL for your tables I would recommend MySQL workbench which is free and a nice tool to use (http://mysqlworkbench.org/)