4 ms·
I think read-only is what most businesses would want, that seems to be how most BI works. Other challenges: 1. Building uniform data connectors suck. GLHF. 2
by reilly3000 7y ago
I think read-only is what most businesses would want, that seems to be how most BI works.
Other challenges:
1. Building uniform data connectors suck. GLHF.
2. Long queries: can you return a promise, then callback to an Apps Script endpoint when the data is ready?
3. Row Limits: I don't see aggregation in your screenshots, that would certainly help. Spreadsheet users know about row limts, just give them good UX and control. Sheets gets sluggish pretty quickly on large data sets, so you may want to have a lower default limit so the UX stays snappy and a warning for large queries.
- ayazhan 7y agoThanks! 1. Yes, We learned that pretty quickly. Especially when working on postgres and mongoDB. And this is the value we’re trying to deliver. As a user, you don’t have to know technical differences between databases and query them all the same way. 2. Interesting idea, we’ll give it a try, thanks! 3. Yes, we don’t have an aggregate feature just yet, working on it. For large datasets, we're thinking about loading a sampled version of the dataset instead for a quick analysis (like histogram analysis and so on). Lowering default limit is interesting, but we are worried it might compromise the experience (if you can only load 10,000 out of 1,000,000 records, you might not be able to do all the analysis you want). Still exploring solutions