I have a basic Django model like:
class Business(models.Model):
name = models.CharField(max_length=200, unique=True)
email = models.EmailField()
phone = models.CharField(max_length=40, blank=True, null=True)
description = models.TextField(max_length=500)
I need to execute a complex query on the above model like:
qset = (
Q(name__icontains=query) |
Q(description__icontains=query) |
Q(email__icontains=query)
)
results = Business.objects.filter(qset).distinct()
I have tried the following using tastypie with no luck:
def build_filters(self, filters=None):
if filters is None:
filters = {}
orm_filters = super(BusinessResource, self).build_filters(filters)
if('query' in filters):
query = filters['query']
print query
qset = (
Q(name__icontains=query) |
Q(description__icontains=query) |
Q(email__icontains=query)
)
results = Business.objects.filter(qset).distinct()
orm_filters = {'query__icontains': results}
return orm_filters
and in class Meta for tastypie I have filtering set as:
filtering = {
'name: ALL,
'description': ALL,
'email': ALL,
'query': ['icontains',],
}
Any ideas to how I can tackle this?
Thanks - Newton
Taking the idea in astevanovic's answer and cleaning it up a bit, the following should work and is more succinct.
The main difference is that apply_filters is made more robust by using
None
as the key instead ofcustom
(which could conflict with a column name).You are on the right track. However,
build_filters
is supposed to transition resource lookup to an ORM lookup.The default implementation splits the query keyword based on
__
into key_bits, value pairs and then tries to find a mapping between the resource looked up and its ORM equivalent.Your code is not supposed to apply the filter there only build it. Here is an improved and fixed version:
Because you are using Q objects, the standard
apply_filters
method is not smart enough to apply your custom filter key (since there is none), however you can quickly override it and add a special filter called "custom". In doing so yourbuild_filters
can find an appropriate filter, construct what it means and pass it as custom to apply_filters which will simply apply it directly rather than trying to unpack its value from a dictionary as an item.I solved this problem like so:
This method feels like a cleaner separation of concerns than the others that I've seen.