Mechanism for handling large Array<?> paged queries

[ryuujo1573]

What is the problem this feature would solve?

Querying a big Array (like 100k items) quickly reaches the response size and is not good for performance.

This is a rather common situation

What is the feature you are proposing to solve the problem?

Implement paged queries to handle the request in small batches

What alternatives have you considered?

No response

[kravetsone]

Wdym???

[ledihildawan]

A common alternative used in scenarios involving large datasets is pagination or infinite scroll, since nearly all programming languages and frameworks are not designed to handle extremely large data retrievals in a single request, whether in terms of memory, bandwidth, or performance.

I believe it's rare (if not impossible) to find a real-world use case where 1 billion records are fetched in a single query, as that would be highly inefficient and extremely taxing on the system.

Paged queries are a natural and widely accepted best practice in cases like this.

[ryuujo1573]

A common alternative used in scenarios involving large datasets is pagination or infinite scroll, since nearly all programming languages and frameworks are not designed to handle extremely large data retrievals in a single request, whether in terms of memory, bandwidth, or performance.

I believe it's rare (if not impossible) to find a real-world use case where 1 billion records are fetched in a single query, as that would be highly inefficient and extremely taxing on the system.

Paged queries are a natural and widely accepted best practice in cases like this.

Thank you for your reply.

You're right for sure. For the op I mean that should we introduce a built-in mechanism for paged queries (on a database / memcache) or not :)

[kravetsone]

A common alternative used in scenarios involving large datasets is pagination or infinite scroll, since nearly all programming languages and frameworks are not designed to handle extremely large data retrievals in a single request, whether in terms of memory, bandwidth, or performance.

I believe it's rare (if not impossible) to find a real-world use case where 1 billion records are fetched in a single query, as that would be highly inefficient and extremely taxing on the system.

Paged queries are a natural and widely accepted best practice in cases like this.

Thank you for your reply.

You're right for sure. For the op I mean that should we introduce a built-in mechanism for paged queries (on a database / memcache) or not :)

Wtf is built-in mechanism for paged queries

[ryuujo1573]

Wtf is built-in mechanism for paged queries

Let me give an example on this.

Simply put, wrap this in a paged-query factory function.

Does this answer your question?

[kravetsone]

Wtf is built-in mechanism for paged queries

Let me give an example on this.

Simply put, wrap this in a paged-query factory function.

Does this answer your question?

And what's u want from Elysia here

[ryuujo1573]

Wtf is built-in mechanism for paged queries

Let me give an example on this.

Simply put, wrap this in a paged-query factory function.

Does this answer your question?

And what's u want from Elysia here

wrap this in a paged-query factory function

for common usage