Manuel Jeckelmann

Hi @mikeengland, thanks for your interest. Let me elaborate a bit on Django version support: From Django 1.8 (LTS) to Django 1.9 there were major changes in the ORM. So,...

I'll re-open this issue to make the desire for MySQL/Maria and Django 1.10 explicit.

@mikeengland while adding tests for MySQL/MariaDB, I stumbled upon an issue regarding timestamp precision with earlier versions of MySQL/MariaDB. So, please make sure you have the maximum precision (which is...

Support for Django 1.10 will come w/ PR #140

In the context of mixing versionable and non-versionable models, it would also be useful to jump to another object version directly from a given object version; e.g.: ``` foo_old =...

+1 for version_as_of(..) ;) -Manuel On Fri, Jan 30, 2015, 17:25 brki [email protected] wrote: > I don't really like time_version as a method name though. > version_as_of(..) perhaps? > >...

@brki Did you start work on this, already?

I think it would be useful to have a section with potential CleanerVersion integrations with frameworks like DRF, in your case. As GitHub issues are searchable and a little bit...

Cool with that - go ahead ;)

Hi @ezheidtmann, Thanks for your contribution. The `SuspiciousOperation` exception is mainly intended to avoid someone adding related objects on non-current objects. As you may have guessed already, we didn't implement...