Django 1.7 support about django-mutant

[charettes]

I'd like to be able to support both but it might be a too much of a burden for the project since this is mostly a single person project.

Plus I'd like to rely on Django's migration autodetector and project/model states instead of dealing with the low level schema alteration API which should clean up a lot of things (mostly in the way we deal with relationships). I'm actually waiting for work to begin on South 2.0 (which might backport most of those useful handlers to Django < 1.7) before taking a final decision.

Would you be interested in helping toward maintaining a backward compatibility shim with Django < 1.7?

[shlomiassaf]

I would be happy to help but progress will be slow because my time is limited, but I will help.

If South 2.0 will do what you say it will basically solve most of the issues.
The problem is, when? I think it will take some time.
South site has no details about it nor the RSS feeds.

My first thought is to branch a new 1.7 repo and work on support for >=1.7.
Where change is needed to support <=1.6 I am thinking monkey patch`s.
When we detect 1.6< we will register the appropriate packages that handle the low level API.
Some cases will require monkey patching.

This is dirty but it will ensure easy transformation when dropping support for 1.6

I am new to 1.7 migration and I need to learn the concept behind it.

Another thing to note, as this is an open source project people might use it with MySQL or MSSQL. (despite the lack of support for DDL transactions)
I managed to get them both working quite good.
There is no support for MSSQL in 1.7 migrations... (this is a minor issue but its there).

[charettes]

I've heard that the MSSQL backend on supporting migrations.

You should really stay away from backend not supporting transactional DDLs, there's no way you can ensure you're not going to shoot you in the foot and get a totally out-of-sync ModelDefinition.

[ogu2]

Thanks for the work you've done so far.

any idea when support for 1.7 would be ready? [or is it already working?]

[charettes]

@tr33house work on 1.7 support should start when it's officially released of before if I find the time.

[amdemas]

Hi! Not to poke a stick at this thread, but is there any light at the end of the tunnel on 1.7 support?

[charettes]

@amdemas I unfortunately haven't found the time to work on 1.7 support yet :/

[dmr]

What is the status of this project? Are you still using it, or is there another project that replaced the project for you?

[charettes]

I'm still using it, but I haven't find the time to port it to 1.7 yet.

[charettes]

Since 1.6 end-of-life is approaching I'll need to port it in the next months.

[dmr]

Thanks for the quick reply, I'm relying on django 1.7 so I'll keep using my own solution for the dynamic properties problem for now

[COLABORATI]

@dmr may I ask what kind of solution you are using? I am too interested in the problem of django dynamic models. Thanks!

[dmr]

@COLABORATI Currently we are using our own implementation, a combination of a jsonfield and a custom jsonschema-like language with validictory for validation and mostly elasticsearch for lookups. If I'd start from scratch I would probably give django-hstore a try.

[COLABORATI]

ah, ok, thanks, I was also looking at django-hstore. Have a nice day!

[charettes]

See #33.