Project

General

Profile

Bug #86

Order None Values Properly

Added by Chris Donati about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Estimated Time:
3.00
Deployment type:
AppScale - self deployed

Description

When using a descending index, we put None values first. This differs from how the SDK does it.

Here's a test that we can add to hawkeye/datastore/CompositeMultipleFiltersOnProperty/test_empty_values:

query = CompositeCars.all().filter('make =', make)\
  .filter('model =', model).filter('color =', color).order('-value')
results = query.fetch(limit=None)
values_fetched = [car.value for car in results]
self.assertListEqual(value_options[::-1], values_fetched)

Also available in: Atom PDF