4 ms·
The syntax follows https://github.com/krisajenkins/yesql/ https://github.com/krisajenkins/yesql/ which works with Clojure. So then the DB queries can be defined
by vii 6y ago
The syntax follows https://github.com/krisajenkins/yesql/ https://github.com/krisajenkins/yesql/ which works with Clojure. So then the DB queries can be defined in a language agnostic way, so you don't need a gateway API to access the DB :)
There are many opportunities to grow this, e.g. transforming the SQL files into stored procedures, and being able to lint and check against a DB schema definition. However, I'm not sure that the indirection step of hiding the SQL away from the code actually makes sense in the long run. A tight coupling allows filters and other optimisations to be easily added to the end of a query, and saves one lookup that is not yet supported in your editor.
- nackjicholson 6y agoHey, thanks for the opportunity ideas! You're totally right about the editor lookup problem. I wrote this project, I use this project in a production setting and not being able to jump to the SQL from code does bother me.