Using South in Django 1.7+

[Remco Gerlich]

I want to run South migrations in a Django 1.7+ installation. I know that's now how it's usually done, but we have a special needs use case.

Our users have SQLite files that model their project; the SQL schema used has changed over time, and users are on many different versions.

Our application is a Django 1.6 site. They provide their files to our application, it changes the Django settings so that one of the databases refers to their SQLite file, and we run South on it to get the schema to the current version. Then our app does its actual work. The users continue to refine their models with their old-schema sqlite files.

Now we want to upgrade our Django version, but we need continue to be able to apply our old migrations :-(.

Can South run on Django 1.7+ at all?

If not, maybe we have to keep some 1.6 installation running somewhere on the backend to upgrade a file to the current situation, and then apply new migrations from there...

Greetings,

Remco Gerlich

[Carl Meyer]

Hi Remco,

On 10/08/2015 04:26 AM, Remco Gerlich wrote:
[snip]

> Can South run on Django 1.7+ at all?

Nope. At least not last I tried, and I don't think anyone has done
anything on it since. It looked like it would need some major updating,
since South integrates closely with the database backends and they
changed in a big way in 1.7.

> If not, maybe we have to keep some 1.6 installation running somewhere on
> the backend to upgrade a file to the current situation, and then apply
> new migrations from there...

Yes, I think that's probably your best bet. You could try your hand at
porting South to 1.7, but I wouldn't expect it to be easy.

Carl