Show HN: DevJoist, database versioning done right

I don't understand how this is an improvement over Rails' migrations or Python's South. Or, maybe, what are cases in which I would consider DJ over built-in migration and schema-management systems?<p>EDIT: ah, perhaps this is just for systems that don't have such native schema migration support (e.g. raw PHP apps)? Though I'm still not sure how comfortable I would be separating schema version from deployed code version.

So I'm kind of ignorant here, but why wouldn't you simply have your schemas stored in vcs and deploy out the upgrade scripts at upgrade time?

So, how would I correlate a specific commit in Git to a version on DevJoist?<p>Until then I'll just use <a href="https://github.com/thuss/standalone-migrations" rel="nofollow">https://github.com/thuss/standalone-migrations</a> with my non-Rails projects.

Do you have an API I could wire into?