4 ms·
What are the problems with South, as you point to? I think those are a big part of the selling point for your project. :) Additionally, could you explain how t
by kmfrk 14y ago
What are the problems with South, as you point to? I think those are a big part of the selling point for your project. :)
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.
- StavrosK 14y agoI will second this. What's wrong with South, currently? By the way, this is the first Kickstarter project I've considered funding.
- Glyptodon 14y agoSouth can often fail for reasons that are surprisingly silly, at least in my experience. Though it's still pretty useful compared to having nothing.
- stevejalim 14y agoIs that with MySQL? I've used it for scores of projects, always with Postgres, and it's never failed me, even if it's been a bit slow when there are lots of rows in play (which isn't really South's fault)
- Glyptodon 14y agoYeah, with MySQL. You've probably got a pretty good point there. If I were to start a site myself one of the first things I'd do is never use MySQL, though it does improve ever so slowly. 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.
- andrewgodwin 14y agoI try to address the key points in the Kickstarter, but essentially South is too fragile (it relies on exactly linear histories) and too verbose (bakes the entire ORM state into every migration) - the main point is to fix those. It's also worth pointing out that this IS the built-in schema migration that's going in in 1.6 or 1.7.
- mladenkovacevic 14y agoYou should reiterate in this thread that you are the originator of South as well so if anyone knows its limitations it should be you :)
- kmfrk 14y agoAlright, alright, have my money then. :)
- antihero 14y agoAre you going to do something about fields needing dependencies? So say you have a django-tinymce field in one of your migrations but remove it later, South will currently still depend on django-tinymce, even though in the database it's just a text field.
- zalew 14y ago> 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? uhmm, it's exactly this project :)
- mhb 14y agoAdditionally, 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? Maybe he added it in the last 7 minutes, but this is answered in the Kickstarter description.