with sheet as (
select \*
from
url('https://docs.google.com/spreadsheets/d/1XGCy0tYU5YcEouO09_ErZIyqjA-VJ4pidLZmMmJkEdk/gviz/tq?tqx=out:csv&sheet=Sheet1&range=A:C', CSVWithNames)
)
select \* from sheet
https://luabase.notion.site/Query-a-Google-Sheet-905da4e981b...https://charlieharrington.com/library/
Click the “I’m feeling lazy” button if you just want to see some example queries.
I also wrote a tutorial, as well, if you’d like to try out roapi yourself:
Also worth checking out https://equals.app/
1 - https://steampipe.io 2 - https://hub.steampipe.io/plugins 3 - https://hub.steampipe.io/plugins/turbot/googlesheets
Does this client do something smart to mitigate that, have the limits been relaxed, or is it still a problem?
The great thing about it is that you get a very versatile admin UI for free. The downsides however are rate limits and the fact that I can't think of any way to build in some sort of safety that would prevent people from accidentally deleting a bunch of data with a mouse click. I would love to hear if anyone has real life experience with the approach.
My experience is that this is always the issue with spreadsheets when you try and grow them out to try and behave like more powerful tools. The same functionality (flexibility etc.) that makes them great for 1-5 people to work on means that it's hard to constrain the system as much as you'd like to when you grow it.
Having said that there are things you can do, like using protected ranges in gsheets that only certain users can edit, or input validation that makes it harder to add bad data. The built in version history is also a handy fall back in case someone does bork the sheet and you catch it in time.
- Baserow[0]
- NocoDB[1]
Also, modern CMSes that are DB-first (or at the very least try their best not to mangle the DB and provide programmatic access) are basically completely overlapped with this use case and can be good as well.
[0]: https://baserow.io
[1]: https://nocodb.com