#musicbrainz

I'm back

it took 1 hour to load the mbdump into the DB

and create the indexes..

it's impossible to execute something I'm asked about a few days ago, which is basically this query: http://www.apaste.info/f8Xm

it takes way too long

Wait

For *every single recording* in the DB? The 10 million of them?

yep

Well yeah, that's likely to take a while

it does finish though, I was just saying.. :P

I need a slighlty different query but I couldn't find a way to express it in SQL in a sane way

(for a specific artist I would understand it, but for every single recording...)

do you remember? I wanted some info about all "songs"

and I asked here what that would be

Yeah, but I thought you'd want them for one artist, heh

(at a time, I mean)

the point is this is getting ALLLLLL the recordings

I was supposed to use the earliest release

but that's not easy to accomplish

becuase the year is in two different tables and you have to do LEAST(...) etc :|

Heh

I mean, for a release_group, I only wanted the songs of its earliest release

instead I'm getting all the songs for simplicity

(where song == recording)

(and nothing else, since you're not getting the artist data or anything)

I'm getting the recording_group mbid, which is my link to artists!

Well, I meant you're not taking the recording artist

But yeah, if you have the ID you can indeed always query for that later

I'm doing so with a different query...

mb's database is too big and complex, I'm taking what I need and caching it in a different schema in pgsql

so then I can drop this DB

err, drop this schema I meant (mb's schema, with over 150 tables, wtf!?)

xD

reosarevok, can you think of any way to limit the recordings to those in the earliest release for each release_group?

I couldn't find out how to filter the recordings like that

mb's schema.. highly normalized

yep, I mean, it's really awesome and well designed

but I'm using only 10% of it, so I'm caching results and dropping the rest

my dad made a normally-delicious dinner, but my stomach is acting up

just had to put duct tape on my charger due to split rubber

it annoys me how poorly designed and overpriced these things are

Hi

By any chance does anyone know about the acoustic fingerprinting for releases?

As in how to create that from CDs, or info from the MB database?

Okay, is anyone out here, or is everyone else otherwise engaged?

sigh

need something, derwin?

he was probably just sighing at the impatience of *!*@gateway/web/*

I'm not sure what that is

HibiscusKazeneko: someone joined from web irc, asked a question, and quit 4 minutes later

I know

I couldn't get to him in time

hmm

HibiscusKazeneko: cheap rubber

good cables, though

yeah, the cable itself appears fine

I have mine rubberless for a year now and it still works

it might be coming unwound, but at least it isn't frayed yet

I just duct-taped the parts I'm touching

do you still cover the wires so they don't catch anything on fire?

12v

what fire?

one previous charger I had became discolored over time

I was worried that the combination of heat and exposed wires would produce sparks

BTW this charger outputs 20V

the last one was lower, I'm not sure by how much

not sure how much fire I can make out of 12-20V

plenty if you leave an unattended book, sock or something near an exposed wire

just dust

I gotta get some sleep. Night all

Hi all, I am looking for some help. I have this error after upgrading to the new version (schema 19)

Caught exception in MusicBrainz::Server::Controller::Root->index "Failed query:

DBD::Pg::st execute failed: ERROR: relation "release_name" does not exist LINE 7: FROM release JOIN release_name name ON release.name=na... ^ at lib/Sql.pm line 83.

how did you upgrade? that sounds like the code is out of date since it's looking for a table which was removed in the schema change

(also #musicbrainz-devel might be better)

@Nikki thanks. I am following the update instructions - git fetch origin, git checkout <latest-git-tag>. then, carton exec -Ilib -- ./upgrade.sh

hm, not sure then :/

I'd suggest asking in #musicbrainz-devel, since the people who might have the answer pay more attention there, although it's quiet right now, not sure if anyone else is around

yeah. Agree! thanks for being a help mate. :)

hilikus_: what url are you fetching the code from? 'git remote show origin' should say either github or bitbucket

I am fetching code from github - Fetch URL: git://github.com/metabrainz/musicbrainz-server.git

okay, that's good then :) what does 'git rev-parse HEAD' say?

b32b2fc23ebb11d50888ea0969d9e2bf27c0a9e2

that's the result. btw, thanks for looking into it. :)

hm, that would indicate the code is up to date at least

did you restart the server after updating? :) ianmcorvidae might have more ideas but he's in #musicbrainz-devel

I didn't restart yet. will going to reboot now. thanks

bitmap: I believe the upgrade steps I've performed was right. But when I roll back DB schema sequence to 18 everything works fine.

bitmap: I changed it back to 19 so that code base and database are all 19. After that, I can update the slave now without any issue. I think restarting my instance resolved the issue. thanks

Server busy, try again later. Blah blah blah....

Yeah :(