Shai Berger wrote:
> On Thursday 09 October 2014 09:53:44 Andrew Godwin wrote:
> >
> > The logic is not too complex, but the feature would need to be
> > dependency-aware and delete any migrations that depended on the updated
> > migration before it re-ran makemigrations; in addition, if no migrat
On Thursday 09 October 2014 09:53:44 Andrew Godwin wrote:
>
> The logic is not too complex, but the feature would need to be
> dependency-aware and delete any migrations that depended on the updated
> migration before it re-ran makemigrations; in addition, if no migration
> name is provided (as to
Either is fine, depends on the dynamic you want to take. Direct to me will
probably get more attention; I don't read -developers nearly as often as I
should.
Andrew
On Thu, Oct 9, 2014 at 12:03 AM, Petri Lehtinen wrote:
> Andrew Godwin wrote:
> > --update was a feature contributed to South that
Andrew Godwin wrote:
> --update was a feature contributed to South that I didn't write, but pulled in
> and everyone found useful; I didn't get it in for the 1.7 release as there
> were
> time constraints, but I'd definitely be open to seeing it re-added.
>
> The logic is not too complex, but the
--update was a feature contributed to South that I didn't write, but pulled
in and everyone found useful; I didn't get it in for the 1.7 release as
there were time constraints, but I'd definitely be open to seeing it
re-added.
The logic is not too complex, but the feature would need to be
dependen
On Thursday, October 9, 2014 12:01:45 AM UTC+3, Curtis Maloney wrote:
>
> Since I didn't know about the update feature in South... can you explain
> how it would be different from migration squashing in 1.7?
>
South's schemamigration --update has very little to do with migration
squashing.
Squa
Since I didn't know about the update feature in South... can you explain
how it would be different from migration squashing in 1.7?
--
C
On 8 October 2014 17:33, Petri Lehtinen wrote:
> Hi!
>
> The database migration system in Django 1.7 is really great and
> seems to work very well. However, s
Hi!
The database migration system in Django 1.7 is really great and
seems to work very well. However, since I'm a long-time South
user, there's one feature that I'm missing: the possibility to
update an existing migration (the --update flag to South's
schemamigration command).
I think it's an imp