3 ms·
True on all counts, but this is designed to be used on the client side, not to replace SQL on the server. An example gives a hint: imagine you have a music play
by haxtra 4y ago
True on all counts, but this is designed to be used on the client side, not to replace SQL on the server. An example gives a hint: imagine you have a music player, and instead of jet-style control panel to search and filter songs, you'd have just a single text input. It's like a terminal for the database.
As for the joints, I didn't need them when I built this, but it shouldn't be a problem to add them.
- gregjor 4y agoSince joins require knowledge of the underlying schema to get right, you probably want to expose database views rather than implement join syntax. Regular users aren't going to understand joins or get them right no matter how simple you make the syntax. I wrote a report generator for end users that uses simplified syntax, and found it was useful to present a standard list of column names rather than the actual names, and to hide the joins altogether. Views can accomplish most of that, especially in a query-only application.