Jan-Jelle Kester

While I still am in favor of a compatibility layer I do want to see your particular solution before accepting these changes. You will hear from me soon.

I do not really like the fact that you do some SQL "fixes", can you elaborate a bit more on your implementation?

I do not agree with you on the migrations part, I think having migrations for these kind of things is a good thing. Hacking in SQL should - in my...

I think a settings switch is still permissable, but as stated above I am not a fan of executing SQL ALTER statements manually outside of migrations (it might very well...

Thanks for your suggestion. It is interesting to see what competing libraries are doing. I am not comfortable with monkey patching model instances to keep some configuration data. This defeats...

Moved to 0.5.0 release to quickly ship improvements for Django 1.10.

Are you sure that auditlog caused this weird behaviour? I can personally guarantee that the Auditlog code does not "hack" (or: monkey patch) any Django code. I recommend you try...

Maybe I'm missing something here. Auditlog should _never_ change the contents of model fields, especially when a model is not registered to be logged. Looking at the 'auditlog-included' example it...

@kbussell I have copied your comments about your solution to the PR description as well.

Can you provide a bit more information?