c# - WebAPI OData $Skip on custom IQueryable double applied -

-

i have implemented custom iqueryable exposed via webapi odata endpoint. structure of controller's get() rather standard:

[enablequery(     allowedqueryoptions = allowedqueryoptions.count                           | allowedqueryoptions.filter                           | allowedqueryoptions.orderby                           | allowedqueryoptions.skip                           | allowedqueryoptions.top)] [odataroute] public pageresult<foo> get(odataqueryoptions<foo> queryoptions) {      var bars = new queryabledata<foo>(_provider);      var result = ((iqueryable<foo>)queryoptions         .applyto(bars,             new odataquerysettings(new odataquerysettings { enableconstantparameterization = false, ensurestableordering = false }))).tolist();     var count = _provider.count;     return new pageresult<foo>(result, null, count); }

the odd behavior seeing, odata $skip in query string applied after pageresult returned. example:

  • if query string contains ?$top=10&$skip=10 there no results return.
  • if query string contains ?&top=12&skip=10 there (2) results returned.

what looking prevent framework(s) applying skip results set since query provider implementing skip. there odataquerysettings can set prevent double application of skip?

edit: upon further investigation, when remove $count=true query string skip (and top) function expected. leads me believe approach implementing $count=true incorrect. debugging sessions appears when $count=true in query options queryable has expression tree applied twice, once return type of long, , again without wrapping countlong expression. have tried returning count on first pass , proper queryable second pass, results in delayed application of skip expression. there seems be fundamental missing here.

while reading through github issues list came across post: odata pageresult method ignoring count parameter when using enablequery attribute #159. appears problem combination of enablequery attribute , parameterized constructor taking odataqueryoptions. using both means implement constructor query options, applying query expressions, framework apply filters can on direction applied attribute; therefore double applying things skip, top , orderby.


Comments

Post a Comment

Popular posts from this blog

python - TypeError: start must be a integer -

-
i trying draw 5 turtles, getting typeerror on line 25. here code: import turtle wn = turtle.screen() redrose = turtle.turtle() color = input("what background color be?") fillcolor_f = input("what color of rose be?") redrose.hideturtle() redrose.speed(30) redrose.penup() redrose.left(180) redrose.forward(175) redrose.right(90) redrose.forward(30) redrose.right(90) redrose.pendown() def drawrose(red): redrose.color("pink") redrose.fillcolor(fillcolor_f) redrose.fill(true) in range(red): redrose.forward(i) redrose.right(49) in range(5): drawrose(redrose) redrose.penup() redrose.forward(350) redrose.right(144) redrose.pendown() redrose.fill(false) drawrose(50) wn.bgcolor(color) i trying draw 5 roses, produces errors. doing in interactivepython.org. you recursively calling drawrose wrong parameter. on line 23 ( for in range(red): ) expect red integer...
Read more

c# - DevExpress RepositoryItemComboBox BackColor property ignored -

-
i have following code almost works properly; private void cbstatus_drawitem(object sender, listboxdrawitemeventargs e) { string item = e.item string; if (item != null) { switch (item) { case "1": e.appearance.forecolor = color.green; e.appearance.backcolor = color.green; break; case "2": e.appearance.forecolor = color.orange; e.appearance.backcolor = color.orange; break; case "3": e.appearance.forecolor = color.red; e.appearance.backcolor = color.red; break; } } } when dropdown shown, items forecolor correct, backcolor remains whatever backcolor of theme is; i.e. if i've got set dark theme, backcolor dark, cells in gridview, rather being green/orange/red. i've tried setting e.appearance.options.usebackcolor trying set e....
Read more

django - Creating multiple model instances in DRF3 -

-
1) create multiple model instances 1 api call, asked here: how create multiple model instances django rest framework? tried solution named in link, no success. i trying upload multiple files in 1 api call. result: files uploaded (only once overwrote perform_create) 1 instance created (if send 2 files, latter created instance). my code: class fileuploadserializer(serializers.modelserializer): def __init__(self, *args, **kwargs): many = kwargs.pop('many', true) super(fileuploadserializer, self).__init__(many=many, *args, **kwargs) class meta: model = fileupload read_only_fields = ('created', 'datafile', 'owner') class fileuploadviewset(viewsets.modelviewset): queryset = fileupload.objects.all() serializer_class = fileuploadserializer parser_classes = (multipartparser, formparser, ) def perform_create(self, serializer): file_list = self.request.data.getlist('file') ...
Read more