4 ms·

At times it might make sense not to use SQL. That is fine. But I think there is a value in learning SQL. Some reasons: * Learning effort to Reward ratio is goo

At times it might make sense not to use SQL. That is fine. But I think there is a value in learning SQL. Some reasons: * Learning effort to Reward ratio is good. A substantial syntax is valid for all of the DBs that support SQL. * Very easy to remember the syntax. I have not used SQL in a long time but I can still write one without much effort (including the nested queries) * Pareto: About 70-80% of data retrieval use-cases are well covered in SQL syntax (or a combination of multiple queries like union, creating temp table, etc) * Tooling: Free & commercial tools which connect to multiple data-sources and provide SQL e.g [1] [1] https://www.jetbrains.com/datagrip/ https://www.jetbrains.com/datagrip/ (I am not associated with jetbrains)

scns 5y ago
Or Idea Ultimate which contains Datagrip's functionality and the other languages they made IDEs for, except CLion (C/++, Rust debugger) and Rider (C/F#). Android Studio can connect to the Apps SQLite db. There is a plugin for Vim to connect to DBs, Written by Tim Pope. Just a content user. (edit) Links for the curious: https://github.com/tpope/vim-dadbod https://github.com/tpope/vim-dadbod There are a UI and completions for it too: https://github.com/kristijanhusak/vim-dadbod-ui https://github.com/kristijanhusak/vim-dadbod-ui https://github.com/kristijanhusak/vim-dadbod-completion https://github.com/kristijanhusak/vim-dadbod-completion