I'm not sure if there'll be an actionable outcome of this, but wanted to raise it for discussion.
We've started supporting some of the PostgreSQL specific fields in Django REST framework, and I ran into a roadblock when adding a new testcase. Unsurprisingly we're not able to test them without also switching the test database to PostgreSQL. As a third party app that's not something I want to have to do - it'd mean a bunch of work, an extra dependency, slower tests, and (unacceptablly) more complication for our contributors. The only way I can see to resolve it would be if we had support for those fields with the sqlite backend. Technically I assume that's feasible - use JSON encoding for storing the data (probably easy), and do awfully non-optimal in-memory filtering for the field-specific lookups (probably very hard). There'd also be the obstacle requiring someone with the time and motivation to make it happen. Options I can see: * The status quo - don't support fields these in SQLite. (I assume this is by far the most likely.) * Support the fields in SQLite, but don't support the lookups. (This'd actually hit the sweet spot for me - I can still test against these fields, and test cases will run just fine, so long as you're not hitting any field specific fitlering in querysets.) * Support the fields and lookups in SQLite. (Sounds highly unlikely.) Any thoughts? Cheers! Tom Aside: I'm not interested in the "you should be testing with the same database as you use in production" gumpf here. It's a third party app. -- 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/f08447af-395c-4fb0-9f01-d2af3b4b8504%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
