#Doooing - expand

1 messages ยท Page 1 of 1 (latest)

sturdy orchid
flat quiver
#

aaahh damnit

#

uh

#

that will become complex ๐Ÿ˜ฆ

#

I guessed something like that

sturdy orchid
#

Yeah, as you can't paginate on expanded items

flat quiver
#

how about, not expanding, then pagination, and retrieving the 3 single products separately?

#

wouldnt that be easier / more performant?

#

or how many objects can I retrieve un-expanded?

#

maybe not even pagination needed?

#

tried. Remove the expand. Still only 10 :(.

#

so whats easier and or more performant -pagination or that search query thing?

#

I think I found it:
limit optional, default is 10

A limit on the number of objects to be returned, between 1 and 100.

#

Funny that, at least the Java api uses a LONG on the limit, that is 100 max. 100 will fit in a long like 1 billion times or so ๐Ÿ˜‰

#

Further update:
Expanding worked with the 19 prices / 3 products we have actually!

#

I still thinking - that means 3 products retrieved for 19 prices.. that is a certain overhead.
Maybe I should instead retrieve the products separately?

#

Is there a way to retrieve the TOTAL count of prices, so that I do not use pagination, but throw an exception of there are more then 100 prices so pagination must be added in such rare case?

sturdy orchid
#

Maybe I should instead retrieve the products separately?
it depends on your use case, I recommend you to do some test

#

so whats easier and or more performant -pagination or that search query thing?
you'll need pagination with search, because you'll get only 10 items per result

sturdy orchid
flat quiver
#

well there are just 19.

sturdy orchid
#

You should design a system that can handle this case and more if that something could happen

flat quiver
#

well, I am trying to. that's why, I need to know the maximum amount of list entries

#

how would you handle pagination otherwise? Paginate until an exception occurs or null is returned???

sturdy orchid