Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selecting Data: Switch .mode and .header statements to be run after the first query #217

nickrsan opened this issue Mar 27, 2018 · 2 comments


Copy link

@nickrsan nickrsan commented Mar 27, 2018

Practicing this today, my partners, who aren't SQL users, were confused when I first did the lesson in the order that it's in, where .mode column and .header on are used before selecting any data, and liked it when I tried a variation later, where I selected data first, showed them that it's hard to read, then ran each command and the select statement in turn, showing the change in output as a result.

As constructed, I think those become magic commands that aren't meaningful enough to be remembered. I think that this change could be created in a way that keeps any time increase to a minimum, and it can also help in discussion of what fields/rows are as learners can see the output shift from a jumble to something structured. I'm curious how other instructors perceive this - I know these commands aren't the point of the exercise, but think learners will want to remember them in the future.

Just a suggestion - if maintainers approve, I'd be happy to submit a pull request with a suggested change. Thanks for creating this - I chose this lesson for my practice in the teacher training because it looked like it was in great shape and would be great for new users, so thanks for making it!

Copy link

@remram44 remram44 commented Mar 28, 2018

Showing what happens if you don't type this, and why we prefer it, is definitely a good idea.

When I gave the lesson, I also mentioned that those could be put in .sqliterc so you don't have to type it every time.

Copy link

@henrykironde henrykironde commented Mar 28, 2018

Both ideas are good. Lets combine them and come out with a description that includes adding these to .sqliterc file and what this file is for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants