Hello Gliders!
Can you help me for a minute, I don’t have glide big tables setup as I like the instant interface with glide tables etc… now with that out of the way can you help me with this question:
Can you use pagination in an http request for Glide Tables? It appears that when i request get rows in make.com it spits out ALL the columns, and ALL the rows. The dataset is too large to work with, over 12MB, and nearing 8000 rows, problem is the data is truncated and I can’t work with it, all it says is Data is too large.
What i’ve done to speed things up and not consume massive data useage in make.com, is I use the datastore to store all the rowID’s of the table I want to use, its way faster in make.com to do this internally, but what I am trying to accomplish is a routine run scenario that creates a true up of this data base to the glide database. Users cannot add rows to my app, it happens all through an API
No. Well, yes and no. Get Rows does support NEXT/CONTINUATION, but you cannot control how many rows are returned with each call. It will always return all rows, up to the maximum of 10,000.
LIMIT is supported with queryTables, but that only works with Big Tables.
If I was you, I would consider moving to Big Tables. My general rule of thumb is that I’ll use Big Tables for anything I expect to grow larger than 10k rows.
1 Like
Well thats unfortunate! Can anyone chime in on how fast the glide big tables will update in the UI compared to native tables?
Big Tables are generally pretty snappy. The only thing that will slow them down is lots of computed columns.
Why don’t you create a test App with a Big Table, import your data and then try for yourself?
Yes i’ll have to do some side by side comparison to ensure it will work, thanks for chiming in Darren, we appreciate it!
Still unfortunate as I have a lot of queries that lookup more than 100 rows of data, this will be a large limiting factor that I can see right now, i’ll have to do some brain storming
That 100 row limit isn’t as restrictive as you might think. It only applies to “unsupported” computed columns. For most column types, you can rollup as many rows as you want. Certainly, with non-computed columns, there is no limit. Although I wouldn’t recommend a joined list of 200,000 rows 
1 Like
OK This alleviates alot of my issue then! I am already in the midst of the multi day testing and migration process of the 150 column beast 
wish me luck!
1 Like
I am finding query + relations cannot be filtered based on anything except a basic column, this is quite limiting at the moment. Has anyone any work arounds? I have some dates calculated that cannot be queried at all
I’ve tried: templating the date, javascript to determine the date, if then else columns to get the date, nothing seems to be able to let me pull a query on the big table from a regular glide table to “fetch” the data I want to see, I am trying to filter all the jobs closed within “this month”, “Last Month”, “Two Months ago”
Essentially the big table is the database, and the regular table is the glide dashboard for each user, row owner specific on all fronts here