Thank you all for all your suggestions and your quick responses. I think
the 1.6-South idea would work, and likewise adding the field by hand using
SQL.
Problem with sqlmigrate is that all we got now is the initial migration,
with all the fields. We don't have a django migration for the new fi
If it's a single database and a single field, is it feasible to just add
the field by hand using SQL?
Greetings,
Remco Gerlich
On Thu, Jul 7, 2016 at 1:05 PM, bobhaugen wrote:
> We're upgrading an app from django 1.4 step-by-step through all the
> versions at least to 1.8. Got a self-inflicted
or use
python manage.py sqlmigrate
to get the sql, which you than can apply manually
On 7 July 2016 at 12:59, Avraham Serour wrote:
> I believe you can checkout your project with a commit still using django 1.6
> with south and run the south migration on the remaining database
>
>
> On Thu,
I believe you can checkout your project with a commit still using django
1.6 with south and run the south migration on the remaining database
On Thu, Jul 7, 2016 at 2:05 PM, bobhaugen wrote:
> We're upgrading an app from django 1.4 step-by-step through all the
> versions at least to 1.8. Got a
We're upgrading an app from django 1.4 step-by-step through all the
versions at least to 1.8. Got a self-inflicted problem with the new
migrations in 1.7.
Before we went to 1.7, we added a new field to a model, and migrated the db
using South. Then when we went to 1.7, we restarted all the migr
5 matches
Mail list logo
