You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Join queries always return 200 result rows by default. Users have to use the LIMIT clause to adjust the result size. This requires specifying a very large number to retrieve all results, which is cumbersome and inefficient.
What solution would you like?
Potential solutions include:
Support for pagination in Join query results.
Implement alternative communication protocol than HTTP REST
Either would allow users to retrieve results in manageable chunks, eliminating the need for specifying large LIMIT values and improving overall efficiency and usability.
Is your feature request related to a problem?
Currently, Join queries always return 200 result rows by default. Users have to use the LIMIT clause to adjust the result size. This requires specifying a very large number to retrieve all results, which is cumbersome and inefficient.
What solution would you like?
Potential solutions include:
Either would allow users to retrieve results in manageable chunks, eliminating the need for specifying large LIMIT values and improving overall efficiency and usability.
What alternatives have you considered?
N/A
Do you have any additional context?
The text was updated successfully, but these errors were encountered: