Nick, thanks for responding.
I've thought about doing that but then run into another issue:
If I request 20 objects and the first 20 were created by the user, the
server will return an empty list.
Internally I suppose I could load like 1000 objects to ensure that
I'll get the necessary 20, but t
I see. So in the event that I had to remove objects from the first 20
and fill it in with results from 20 - 40, I would return that number
so the client would know to request from say,
23 - 43 (in case I had to add 3 to fill it up to 20 results).
That seems like it could work, I'll give that a sh
Why don't you simply use the user as parent?
On 19 Jun., 22:15, coltsith wrote:
> I see. So in the event that I had to remove objects from the first 20
> and fill it in with results from 20 - 40, I would return that number
> so the client would know to request from say,
>
> 23 - 43 (in case I had
@dflorey
because that would result in binding the application to entity group
limitations. which don't scale that well
On Jun 21, 4:15 am, dflorey wrote:
> Why don't you simply use the user as parent?
>
> On 19 Jun., 22:15, coltsith wrote:
>
>
>
> > I see. So in the event that I had to remove o
On 10-06-19 20:11, coltsith wrote:
> Nick, thanks for responding.
>
> I've thought about doing that but then run into another issue:
>
> If I request 20 objects and the first 20 were created by the user, the
> server will return an empty list.
>
> Internally I suppose I could load like 1000 objects
