Data and Package Limits
# off-topic
c
Data and Package Limits
I am on the free plan. Can this be fixed with the paid plan. I have an issue with the 1000 row limit on data package. I changed the API setting to 5001 on UI but it is being ignored. Please Help
g
This is a bug right now
c
I am doing a large POS for 1000 storefronts. Is there a fix or a workaround? or should i not bother and use something else?
g
Until they fix it you would need to do multiple requests using .range(0,999) and then .range(1000,1999).
YOu should also email them as they might be able to just set for your instance as it is likely a UI problem
c
I did a little to get their attention. I could do a 1000 backlinks and articles on the bug that they have not even responded to..lol
g
You contacted support email? I have no idea what your data you need to fetch is and what your coding environment is, but it seems pretty simple to create a function that breaks up the api request into batches in a loop as a work around ( it is all just going into an array) if you have a product launched/near launch. If you have complex data I assume you will need to be on a paid plan if you plan to fetch large chunks of data from many clients. Part of the reason for the limit is performance of the data base with large requests and a free plan likely won't get far with many users and many thousands of record requests in one API query. As an aside, and I don't have any relationship with Supabase, your last comment almost sounds like an extortion attempt to get help, which seems counter productive for an issue such as this, IMO. Good luck!
c
Y i thought to try the paid plan to see if it works
I wonder if anyone that has reported has a paid plan
I have done all the regular attempts but its been 2 weeks with no response
I wouldn't say its extortion to bring attention to an issue
If it gets fixed faster its a benefit to everyone
g
Clearly the issue is logged in github, if you have emailed them I can understand your frustration.
Post to the github issue as it gets bumped and I know the founders are looking at the top issues.
c
I guess the top issues will be the ones the scream the loudest
g
As in most cases...lol but I've seen them knocking off/commenting on the latest issues the past couple of days. I'd also make sure your query is simple enough underload to be bringing back a single large http request (both for query table tie up and cost of data on with wire). I have a simple app, but each user can have 10000 or more notes, no way I want them to ever fetch them all at once, especially more than once...
c
ya
I got support they say they can change the setting. Where is the project ID at?
g
well I think it is your URL, but it is late.