Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Max rows in API Settings doesn't work on local development #993

Open
danielvoelk opened this issue Mar 25, 2024 · 0 comments
Open

Max rows in API Settings doesn't work on local development #993

danielvoelk opened this issue Mar 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@danielvoelk
Copy link

Describe the bug

In my config.toml I'm settings the max rows:

max_rows = 1000000

But the value is not applied. It only returns 1000 rows.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Set max rows to a higher value than 1000
  2. Fetch data from a table with more than 1000 rows
  3. See that only 1000 rows will be returned

Expected behavior

I exptected to receive all rows, until a maximum of 1000000.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

  • OS: [e.g. macOS, Windows]
  • Browser (if applies) [e.g. chrome, safari]
  • Version of supabase-js: 2.39.2
  • Version of Node.js: v18.17.0

Additional context

In my staging and production environment it works. Only the local development environment ignores the max_row configuration.

@danielvoelk danielvoelk added the bug Something isn't working label Mar 25, 2024
@saltcod saltcod transferred this issue from supabase/supabase Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant