Additionally, could you explain how the project will not be obviated by Django's plans to implement built-in schema migration in, I think, 1.6 or 1.7?
You taken on one of the most important aspects of managing Django services, so I'm genuinely interested, but I just want to know what the thinking is behind this.
It's also worth pointing out that this IS the built-in schema migration that's going in in 1.6 or 1.7.
uhmm, it's exactly this project :)
Maybe he added it in the last 7 minutes, but this is answered in the Kickstarter description.
By the way, this is the first Kickstarter project I've considered funding.
In the latest version(beta?) you can actually have a column with 'default current_timestamp' and a column with 'on update current_timestamp' in the same table after years of only being able to have 1 column per table auto that way.
I don't remember the details, but I think I had to fill a column with zeros all the way down just to drop the whole column in the migration anyway or something along those lines.