Hi everybody, Recently I've begun to use the PostgreSQL specific fields introduced in Django 1.8. My codebase actually uses the special fields (HStoreField and ArrayField mostly) frequently enough such that I cannot run my test suite on an in memory SQLite database -- I have to run on a PostgreSQL instance.
Running my tests on PostgreSQL is fine, but I miss the zippy performance of an in memory SQLite database. If, say, my test code *cannot *be refactored itself, what would be your suggested route for test speed improvement? I see this outstanding django ticket for UNLOGGED postgres tables <https://code.djangoproject.com/ticket/24306>, and also some work by aaugustin towards adding a `--parallel` option to the django tests <https://github.com/django/django/pull/4063>. Another thought I had would be creating "dumb" versions of the PostgreSQL fields that worked in SQLite. I realize, of course, that by using `django.contrib.postgres`, I should expect to sacrifice Django's "plug and play database backends" -- still curious as to your thoughts of improving test speed for projects that use postgres specific fields. Thanks! -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/32aa98c9-a05f-456f-bd0e-96d324104448%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
