On Thursday, 21 April 2016 18:51:48 UTC+10, Marcin Nowak wrote:
>
> If you're building some report-like queries, or any static queries, I
> would suggest to use raw sql.
> You can optionally wrap results with model instances using
> Model.objects.raw().
>
Thanks Marcin. Yeah, good call perhap
Thanks for the comment Matt. I wasn't trying to change anything in the
database, it was just that Django wanted the django_migrations table to
exist, but it didn't, and the db was read-only for safety during testing.
Could well be that I wasn't using fake properly, I'm not sure, but I'd
still
+1 for disabling migrations completely - for several reasons.
1. Right now, I'm trying to run tests against a production database with
runserver, in *read-only* mode - but it fails because it can't create the
django_migrations table. (I'm in the process of upgrading from Django 1.4
to 1.8, so
3 matches
Mail list logo
