Show HN: ESQLate – Build minimum viable admin panels with just SQL
1–10 of 83 posts
Re: Show HN: ESQLate – Build minimum viable admin panels with just SQL
#2Re: Show HN: ESQLate – Build minimum viable admin panels with just SQL
#3Tools like these are a viable, low-code (to use a hyped-up term) alternative to creating full-blown back-ends with all the boilerplate code that comes with them. Often these back-ends add little more than a REST API or a simple CRUD interface on top of an SQL database.
RDBMS on the other hand are immensely powerful tools that unfortunately more often than are used for little more than simple data storage.
Re: Show HN: ESQLate – Build minimum viable admin panels with just SQL
#4Re: Show HN: ESQLate – Build minimum viable admin panels with just SQL
#5Interesting idea. Are you doing anything to protect against sql injection attacks?
Re: Show HN: ESQLate – Build minimum viable admin panels with just SQL
#6Interesting. How would you make this to support one-to-many/many-to-many relationships?
That's simply how SQL deals with 1:n and n:m relations.
Re: Show HN: ESQLate – Build minimum viable admin panels with just SQL
#7Interesting. How would you make this to support one-to-many/many-to-many relationships?
Re: Show HN: ESQLate – Build minimum viable admin panels with just SQL
#8We use it to get more insight in our data. It does not allow a user to enter anything.
Basically my app only uses a list of queries. To allow that any selected field is clickable, the result field should be like 'report|name|field,field' so the app knows this is a special link (report) refering to another defined query ('name') and should be passed some values (record specific, here 'field,field').
Re: Show HN: ESQLate – Build minimum viable admin panels with just SQL
#9Nice work. I have also build a (mysql) sql based dashboard for our internal use. It mainly shows agregated lists of data and allows to click on many items to see more details. We use it to get more insight in our data. It does not allow a user to enter anything. Basically my app only uses a list of queries. To allow that any selected field is clickable, the result field should be like 'report|name|field,field' so the…