blocks|key|626554|text|不幸的是没有。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|626555|问题是Tastypie的ModelResource类只使用QuerySet的filter()方法，也就是说，它没有使用应该用于负面滤镜的exclude()。不过，没有filter()字段查找会导致求反。有效的查找是(在此SO+post之后)：|offset|length|626556|exact
iexact
contains
icontains
in
gt
gte
lt
lte
startswith
istartswith
endswith
iendswith
range
year
month
day
week_day
isnull
search
regex
iregex|code-block|syntax|javascript|626557|然而，实现对"__not_eq“之类的东西的支持应该不是那么难。您所需要做的就是修改apply_filters()方法，并用"__not_eq“将过滤器与其他过滤器分开。然后，您应该将第一个group传递给exclude()，将其余的传递给filter()。|626558|类似于：|626559|def+apply_filters(self,+request,+applicable_filters):
++++"""
++++An+ORM-specific+implementation+of+``apply_filters``.

++++The+default+simply+applies+the+``applicable_filters``+as+``**kwargs``,
++++but+should+make+it+possible+to+do+more+advanced+things.
++++"""
++++positive_filters+=+{}
++++negative_filters+=+{}
++++for+lookup+in+applicable_filters.keys():
++++++++if+lookup.endswith(+'__not_eq'+):
++++++++++++negative_filters[+lookup+]+=+applicable_filters[+lookup+]
++++++++else:
++++++++++++positive_filters[+lookup+]+=+applicable_filters[+lookup+]

++++return+self.get_object_list(request).filter(**positive_filters).exclude(**negative_filters)|626560|而不是默认的：|626561|def+apply_filters(self,+request,+applicable_filters):
++++"""
++++An+ORM-specific+implementation+of+``apply_filters``.

++++The+default+simply+applies+the+``applicable_filters``+as+``**kwargs``,
++++but+should+make+it+possible+to+do+more+advanced+things.
++++"""
++++return+self.get_object_list(request).filter(**applicable_filters)|626562|应支持以下语法：|626563|someapi.com/resource/pk/?field__not_eq=value|626564|我还没有测试过。它可能也可以以更优雅的方式编写，但应该能让您上手:)|626565|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/687295/how-do-i-do-a-not-equal-in-django-queryset-filtering^0|0|32|7|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@$D|1A|E|1B|1|1C]]|A|$]]|$1|F|3|G|5|H|7|1D|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|A|$]]|$1|O|3|P|5|H|7|1G|8|@]|9|@]|A|$I|J]]|$1|Q|3|R|5|6|7|1H|8|@]|9|@]|A|$]]|$1|S|3|T|5|H|7|1I|8|@]|9|@]|A|$I|J]]|$1|U|3|V|5|6|7|1J|8|@]|9|@]|A|$]]|$1|W|3|X|5|H|7|1K|8|@]|9|@]|A|$I|J]]|$1|Y|3|Z|5|6|7|1L|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]]]

Unfortunately there's not.

The problem is that Tastypie's ModelResource class uses the filter() method of the QuerySet only, i.e. it does not use exclude() which should be used for negative filters. There is no filter() field lookup that would mean negation though. The valid lookups are (after this <a href="https://stackoverflow.com/questions/687295/how-do-i-do-a-not-equal-in-django-queryset-filtering">SO post</a>):

<pre><code>exact
iexact
contains
icontains
in
gt
gte
lt
lte
startswith
istartswith
endswith
iendswith
range
year
month
day
week_day
isnull
search
regex
iregex
</code></pre>

However it shouldn't be so hard to implement the support for something like "__not_eq". All you need to do is to modify the apply_filters() method and separate filters with "__not_eq" from the rest. Then you should pass the first group to exclude() and the rest to filter().

Something like:

<pre><code>def apply_filters(self, request, applicable_filters):
 """
 An ORM-specific implementation of ``apply_filters``.

 The default simply applies the ``applicable_filters`` as ``**kwargs``,
 but should make it possible to do more advanced things.
 """
 positive_filters = {}
 negative_filters = {}
 for lookup in applicable_filters.keys():
 if lookup.endswith( '__not_eq' ):
 negative_filters[ lookup ] = applicable_filters[ lookup ]
 else:
 positive_filters[ lookup ] = applicable_filters[ lookup ]

 return self.get_object_list(request).filter(**positive_filters).exclude(**negative_filters)
</code></pre>

instead of the default:

<pre><code>def apply_filters(self, request, applicable_filters):
 """
 An ORM-specific implementation of ``apply_filters``.

 The default simply applies the ``applicable_filters`` as ``**kwargs``,
 but should make it possible to do more advanced things.
 """
 return self.get_object_list(request).filter(**applicable_filters)
</code></pre>

should allow for the following syntax:

<pre><code>someapi.com/resource/pk/?field__not_eq=value
</code></pre>

I haven't tested it. It could probably be written in more elegant way too, but should get you going :)

blocks|key|411522|text|我已经为此打开了一个bug，并在这里提供了一个简单的解决方案：https://github.com/toastdriven/django-tastypie/issues/524|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|411523|添加“！”可能更好。字段名称末尾的字符，如您在问题中所做的那样...|411524|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/toastdriven/django-tastypie/issues/524^0|V|1L|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I've opened a bug for this and provided a simple solution here: <a href="https://github.com/toastdriven/django-tastypie/issues/524" rel="nofollow">https://github.com/toastdriven/django-tastypie/issues/524</a>

It would probably be nicer to add the '!' character at the end of the field name as you've done in your question ...

blocks|key|626699|text|另一种不需要更改代码的方法是将iregex与inverse+matching结合使用|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|626700|http://HOST/api/v1/resource/?format=json&thing__iregex=%5E((?!notThis).)*$|code-block|syntax|javascript|626701|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/406408/56069^0|M|G|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Another way to do this without code changes is to use a iregex with <a href="https://stackoverflow.com/a/406408/56069">inverse matching</a>

<pre><code>http://HOST/api/v1/resource/?format=json&amp;thing__iregex=^((?!notThis).)*$
</code></pre>

blocks|key|626756|text|注意到戈尔诺上面的答案:似乎只有当你不使用MySQL后端时，这才能起作用。请参见：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|626757|#1139+-+Got+error+'repetition-operator+operand+invalid'+from+regexp|offset|length|626758|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/18317183/1139-got-error-repetition-operator-operand-invalid-from-regexp^0|0|0|1V|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Note on Gorneau's above answer: seems like this only works if you're not using a MySQL backend. See:

<a href="https://stackoverflow.com/questions/18317183/1139-got-error-repetition-operator-operand-invalid-from-regexp">#1139 - Got error &#39;repetition-operator operand invalid&#39; from regexp</a>

blocks|key|626790|text|我使用exclude()来避免某些值。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|626791|Person.filter(name="Tim").exclude(state="Down");|code-block|syntax|javascript|626792|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I use exclude() to avoid some values. For example:

<pre><code>Person.filter(name="Tim").exclude(state="Down");
</code></pre>

Is there a negation filter available by default. The idea is that you can do the following in the django ORM:

<pre><code>model.objects.filter(field!=value)
</code></pre>

How can I do that in tastypie if that is even possible. I tried:

<pre><code>someapi.com/resource/pk/?field__not=value
someapi.com/resource/pk/?field__!=value
someapi.com/resource/pk/?field!=value
</code></pre>

And all of them given me errors.

Tastypie Negation Filter

MySQL

默认情况下是否有可用的否定过滤器。我们的想法是，您可以在django ORM中执行以下操作：model.objects.filter(field!=value)如果这是可能的，我怎么能在tastypie中做到这一点呢？我试过了：someapi.com/resource/pk/?field__not=valuesomea...

问Tastypie否定滤波器
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Tastypie否定滤波器EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Tastypie否定滤波器
EN