Retool Database
21–30 of 55 posts
Re: Retool Database
#22I've been using Retool Database inside a Retool Workflow and I find my update queries don't seem to resolve in the workflow, although I can see the updates in the table. I've just chalked it up to beta status, but since y'all are here I thought I might ask if this is a known issue or if I should reach out to support. Edit to add: really killer addition to the product, keep up the great work
Re: Retool Database
#23I've been using Retool Database inside a Retool Workflow and I find my update queries don't seem to resolve in the workflow, although I can see the updates in the table. I've just chalked it up to beta status, but since y'all are here I thought I might ask if this is a known issue or if I should reach out to support. Edit to add: really killer addition to the product, keep up the great work
Re: Retool Database
#24I think Retool is awesome - though last time I think I didn't see a way to allow clients to have access to certain views. We have some databases we'd love to generate views for client access, but we don't need them to have full blown accounts. Is that something on the horizon?
(PM at Retool) Yes! We recently shipped Retool Embed to enable you to build settings pages, dashboards, and UIs in Retool and embed them securely into your client-facing apps. You can learn more about Embed here and sign up for the beta: https://retool.com/products/embed We’re also working on a solution to let you build full-stack client portals in Retool. I’m antony@retool.com if you want to chat!
Re: Retool Database
#25Hi HN! I’m the lead engineer on Retool Database. Spreadsheets are often used as “poor man’s databases”—they’re quick to get started, but fall apart when you need data integrity, validation, and the ability to query/filter data. This is why I am so excited about this launch - Retool Database gives you the power of Postgres with the “getting started” speed of a spreadsheet. No setup required. We've also spent a lot of…
Re: Retool Database
#26Hi HN! I’m the lead engineer on Retool Database. Spreadsheets are often used as “poor man’s databases”—they’re quick to get started, but fall apart when you need data integrity, validation, and the ability to query/filter data. This is why I am so excited about this launch - Retool Database gives you the power of Postgres with the “getting started” speed of a spreadsheet. No setup required. We've also spent a lot of…
How do indexes work? Do you design them yourself or do they get automatically added based on some kind of heuristics?
But I would have to say - modern day databases are so fast that you probably won't notice the performance of adding indexes until at least 100k+ rows in a table and/or you have very high read throughput on that particular table.
Re: Retool Database
#27Are there good video resources for Retool in general, I looked at some youtube videos and found mostly creating a basic database view with a form. Any more substantial examples?
There are some URLs on a table, I want to select them and I want to make an API call to the selected URLs. There are a few discussions on their community website and all point to one documentation piece. I still haven't figured out how to do this. I don't want open a thread because I know I am going to be asked to read the documentation.
Google "multiple api request retool".
Re: Retool Database
#28Earlier quoted context omitted.
How do indexes work? Do you design them yourself or do they get automatically added based on some kind of heuristics?
We don't do anything automatic like that (yet?), you will have to add indexes manually. But I would have to say - modern day databases are so fast that you probably won't notice the performance of adding indexes until at least 100k+ rows in a table and/or you have very high read throughput on that particular table.
Re: Retool Database
#29Earlier quoted context omitted.
We don't do anything automatic like that (yet?), you will have to add indexes manually. But I would have to say - modern day databases are so fast that you probably won't notice the performance of adding indexes until at least 100k+ rows in a table and/or you have very high read throughput on that particular table.
You'll see a performance benefit way before 100k rows depending on the size of each row, especially with sorting. It might save you guys a ton of CPU hosting wise, depending on how this all works, to track slow queries and auto add indexes. Way worth the write overhead in most cases.