> Are other developers interested in "readonly unitests on live data", too?
At our company we mostly test our Django apps with "live" data for
various reasons.
Our process is roughly following: 1. we make a sql-dump of the current
production data (or part of it if it's REALLY big) and move it t
Thank you Karen for your work.
Some weeks ago I wanted to write an "always_rollback" decorator, but found
that it was not that easy, since Postgres transactions can't be nested. The
first COMMIT commits everything. [1]
I want to run readonly unittests on my live data. I looked at your
patch, and
