Is Johnny Cache compatible with PostgreSQL autocommit?

[AudriusButkevicius]

The docs explain that this is a tricky part:
http://pythonhosted.org/johnny-cache/queryset_cache.html#transactions

But I am struggling to understand if autocommit causes any issues for Johnny?
Or does it make Johnny's life easier?

[AudriusButkevicius]

Also, just to make this clear, TransactionMiddleware is not used in my case.

[jself]

Autocommit, at least prior to 1.6, does not cause any issues with Johnny.
We're still working on 1.6 support unfortunately, but it'll be transparent
as well.

On Mon, Nov 25, 2013 at 8:22 AM, Audrius Butkevicius <
notifications@github.com> wrote:

Also, just to make this clear, TransactionMiddleware is not used in my
case.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-29200837
.

[AudriusButkevicius]

By saying prior 1.6 do you mean prior Johnny introduced support for Django 1.6, or Django versions prior 1.6?

In case it's the first case, what is the last commit usable by 1.5 with autocommit on?

[jself]

Django versions prior to 1.6, Johnny doesn't yet support Django 1.6

On Mon, Nov 25, 2013 at 11:37 AM, Audrius Butkevicius <
notifications@github.com> wrote:

By saying prior 1.6 do you mean prior Johnny introduced support for Django
1.6, or Django versions prior 1.6?

In case it's the first case, what is the last commit usable by 1.5 with
autocommit on?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-29217068
.

[AudriusButkevicius]

Thank you!
I suggest mentioning this in the docs.