Jacek Tomaszewski

Well, even `HStoreField` would suit this case. However, as we aim to maintain compatibility with MySQL and SQLite databases as well, it's unlikely that we would use this feature. Maybe...

Well, we still support Django >= 1.4, so 1.5 and 1.6 should work properly. I assume your failing scenario looks like this: manager with MRO `NewMultilingualManager > MultilingualManager > CustomManager...

Can you please provide more info, a minimal model with translation that's causin a problem?

I'm amazed how similary we think. :) I had been thinking about the same issue about the time of update_translation_fields fix. I wrote the solution and concluded it is possible...

However, I wonder about one thing: we have got rid of Rule 3, because: - it was no more needed as MultilingualManager and other changes were introduced - **there were...

As you can see, the code was already written two weeks ago. :) I feel this change needs more tests, especially a few regarding admin adding/changing. And nice conclusion about...

I see. We can (probably) force `MT` to keep original field intact (code is ready, but not tested completely). Would this be sufficient in your case? The third party app...

Fine, you can be the beta tester then. ;) I've rebased the `preserve_original` branch against master (lots have changed since the code was written (about a year passed!)). Try this...

If a field is "not null", then it's default value (the one returned from field's `get_default()`) cannot be None, so this shouldn't happened.

The second commit should address the objects adding.