andrewgodwin

10 ms·

31.
by andrewgodwin 13y ago
No, this is a complete rewrite and a different way of doing migrations than South currently does. There should also be a South 2 eventually that is mostly compatible with this new migration design, for those stuck on older Django.
32.
by andrewgodwin 13y ago
For anything on Django 1.7 (the version it will come out in), yes, South will no longer be needed. Older versions of Django should get a South 2 in the next few months with a lot of this code backported.
33.
by andrewgodwin 13y ago
I'd like to point out that this is just a first working version, and there's still some work left to do, but I'm very relieved this is finally merged!
34.
by andrewgodwin 13y ago
I've seen RDS have significant per-query overhead, and some very, very variable read times - in particular, some simple SELECTs randomly taking > 10s every so often.
35.
by andrewgodwin 13y ago
Sad to see the recommendation to use MySQL - in my experience RDS hasn't been worth the effort - but I'm probably biased since I already invested the time in automating PostgreSQL replication setup.
36.
by andrewgodwin 14y ago
Hi Greg, There's no books or anything, alas, nor is there a very good corpus of material on this field - there's a few good talks out there, but I've not seen a great deal of written material. Perhaps I need to write a book as well? Not sur
37.
by andrewgodwin 14y ago
I already have written code for this several times in the past for the basic constraint types, but not the where clauses - I'll check it out. Thanks!
38.
by andrewgodwin 14y ago
You're more than welcome, thanks for contributing! It's companies like yours that help such a good ecosystem exist.
39.
by andrewgodwin 14y ago
You won't need to tell other machines that there's a new migration set - they'll just realise and migrate appropriately (new machines on the new initial, old ones on the left-over old ones until they're all done and you can remove them).
40.
by andrewgodwin 14y ago
The Django Software Foundation and I considered it, but Kickstarter is really well-designed for making new projects and is a trusted brand for payments. Building our own would have taken both time and having to get a merchant account workin
41.
by andrewgodwin 14y ago
So the situation here is indeed interesting - I understand your concern. I've asked all the other core contributors to Django their opinions on this and there's been resounding support from them, so that's not a concern. I also have a day a
42.
by andrewgodwin 14y ago
If it gets that high, I'll likely give some back to the DSF, yes, or put it towards other core feature projects. Or perhaps just have the next DjangoCon sponsored by "Schema Migrations".
43.
by andrewgodwin 14y ago
I know. So happy.
44.
by andrewgodwin 14y ago
Part of this is coming up with a new spec for Django field types to allow this stuff to work better, so that'll hopefully do what you want.
45.
by andrewgodwin 14y ago
Thanks a lot - your contribution is much appreciated! I hope this helps set a trend.
46.
by andrewgodwin 14y ago
Exactly, the value here is in linking it directly to the models and apps paradigm of Django. South already does this, and people love it, so it seems reasonable to continue down that path and make it even better.
47.
by andrewgodwin 14y ago
South is actually based on ActiveRecord's migrations a little bit (or rather, it was 4 years ago) but the key difference is autodetection of changes - Rails models are essentially declared via migrations, while Django ones are created in a
48.
by andrewgodwin 14y ago
I 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 w
49.
by andrewgodwin 14y ago
Worth mentioning that if someone wants to ask me (I'm running this) questions about this I'll be checking here!
50.
by andrewgodwin 14y ago
That's how I thought it'd work, just curious. Looking forward to reading up how it works - I hope it's not too fragile.
51.
by andrewgodwin 14y ago
Interesting - I was trying to get this concept to work a few years ago after I got a live SVN/Mercurial translator working, but it was very hard due to all the differences they note in this post. One thing they don't mention is "octopus mer
52.
by andrewgodwin 14y ago
I'm curious to see how this compares to MRI/Rubinius/JRuby once it's feature-complete; the PyPy vs. CPython benchmarks these days are pretty convincing.
53.
by andrewgodwin 14y ago
This is a very interesting point (re: the guilt especially) - sometimes I'm almost dissuaded from releasing code because in the end it might have a net negative impact on my life. There's even stories of people hunting down email addresses
54.
by andrewgodwin 14y ago
However, in the reverse way, the migrations defining the models (as in Rails) often leads to mismatches as well. There's no easy solution to this problem, alas. When model-based migrations work, they work really well, and help reinforce cod
55.
by andrewgodwin 14y ago
Backwards migrations are really only designed for quick testing in development - you really shouldn't be running them in production unless you just made a major screwup. It's entirely possible to shoot yourself in the foot, but that's also
56.
by andrewgodwin 14y ago
There is, hopefully in a couple of releases' time. There are some posts I made to the mailing list about it a while ago - I can't look them up quickly though - and a talk I did at DjangoCon this year.
57.
by andrewgodwin 14y ago
Unfortunately the permissions thing is really, really tough to fix - and not using Django permissions myself nor in any work projects, one that's rarely high on my priorities, alas. For Git stuff, just make sure you're aware of who is writi
58.
by andrewgodwin 14y ago
(Author of South here) Nice article - good set of common pitfalls, too. The multiple people one is especially tricky for people when they first encounter it, it seems. I'm hoping I can resolve some of these issues (like the permissions thin
59.
by andrewgodwin 14y ago
Nice to see this appear here! Probably worth pointing out that we spent a few weeks preparing for this move - it's not something you can pull together in a few days (unless you're very laissez-faire about your data).
60.
by andrewgodwin 14y ago
This article seems particularly biased against Intel - it gets down to what are almost character attacks at points. I'd love to see a more level-headed analysis of the Ultrabook space. There's over a hundred different ones now (which may in

More ›