I like this, but as mentioned, it's a shame that it starts of with a MySQL specific command, SHOW tables
thanks for the feedback! Will change it
Show HN: SQL Trainer – Learn SQL by doing live data exercises
21–30 of 50 posts
Re: Show HN: SQL Trainer – Learn SQL by doing live data exercises
#22Hi,
My name is Eugene and we made this little online SQL language trainer to help non-programmers to learn basic SQL queries. And more important, it shows the result of query entered.
Any suggestions and comments are welcome!
and many thanks for all the suggestion already made! And seems like we should better remove MySQL specific command from the very first question.
Re: Show HN: SQL Trainer – Learn SQL by doing live data exercises
#23I learned everything from: sqlteaching.com It was created in a hackathon and uses sql.js, you can also create your own exercises through sql.js if you know a thing or two about web development ;)
SQL Teaching itself is also open source!
https://github.com/rhc2104/sqlteaching
(Creator of SQL Teaching)
Re: Show HN: SQL Trainer – Learn SQL by doing live data exercises
#24Earlier quoted context omitted.
Is there an alternative (like a command to list all tables and which works on all DBMS)? I mean using a specific sqlite/oracle/tsql/... command wouldn't be any better.
No, there isn't. But I don't see the need to start with these commands anyway. Or if the OP really feels like that's a necessary starting point, it would be great to have an option in the future to select what DBMS you're using. I wasn't intending to bash the work, but sticking to a single DBMS really limits the utility of what seems like it could be very general resource.
I like the idea of being able to select which dialect one wants to learn and maybe a table listing the most prominent differences (like LIMIT vs. TOP) at the end, would be nice too.
Re: Show HN: SQL Trainer – Learn SQL by doing live data exercises
#25Hi, My name is Eugene and we made this little online SQL language trainer to help non-programmers to learn basic SQL queries. And more important, it shows the result of query entered. Any suggestions and comments are welcome! and many thanks for all the suggestion already made! And seems like we should better remove MySQL specific command from the very first question.
Maybe not remove it but perhaps have a choice of SQL 'flavor'.
That would be very useful, aka user chooses Oracle, MySQL, MS-SQL, etc.
Re: Show HN: SQL Trainer – Learn SQL by doing live data exercises
#26I like this one very much: http://sql-ex.ru/
Major part of questions is based on MS SQL Server though.
Re: Show HN: SQL Trainer – Learn SQL by doing live data exercises
#27Some other similar tools I added to my notes from a similar thread: https://news.ycombinator.com/item?id=17905666
Interactive PostgreSQL SQL Tutorial - https://chartio.com/learn/sql/
Select STAR SQL - https://selectstarsql.com/
SQL Bolt - https://sqlbolt.com/ - Learn SQL with simple, interactive exercises
SQL Window functions - https://www.windowfunctions.com/
PostgreSQL Exercises - https://pgexercises.com/
SQL Zoo - http://sqlzoo.net/
SQL Teaching - https://www.sqlteaching.com/
Re: Show HN: SQL Trainer – Learn SQL by doing live data exercises
#28This is nice, but it's unfortunate that it starts off with commands specific to MySQL.
Is there an alternative (like a command to list all tables and which works on all DBMS)? I mean using a specific sqlite/oracle/tsql/... command wouldn't be any better.
In theory `information_schema` is supposed to be universal, so you could do `select table_name from information_schema.tables`. However, getting useful information out of `information_schema` tends to require fairly complex queries and still has quirks and differences between databases.
Re: Show HN: SQL Trainer – Learn SQL by doing live data exercises
#29Re: Show HN: SQL Trainer – Learn SQL by doing live data exercises
#30Hi, My name is Eugene and we made this little online SQL language trainer to help non-programmers to learn basic SQL queries. And more important, it shows the result of query entered. Any suggestions and comments are welcome! and many thanks for all the suggestion already made! And seems like we should better remove MySQL specific command from the very first question.
Nice! Would love to see this, but for complex queries.