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

Move Backing Up with SQL to the top of the Creating tables... episode? #135

Open
libcce opened this issue May 18, 2021 · 5 comments
Open
Assignees

Comments

@libcce
Copy link
Contributor

libcce commented May 18, 2021

Should "Backing Up with SQL" in "Creating tables and modifying data" be moved to the top of the episode:
https://librarycarpentry.org/lc-sql/09-create/index.html

In other words, before you make changes to your database... make sure you back up and version your database. Instead of "Be very careful when doing this: if you drop the wrong table, hope that the person maintaining the database has a backup, but it’s better not to have to rely on it."

I also wonder if this should be an exercise, that we can highlight backing up your SQL and that versioning is an option with the caveats. Instead of the exercise we can include the action to dump the database and save it with the ISO 8601 date and name?

@mimkes
Copy link
Contributor

mimkes commented May 18, 2021

Yes, your thought all make sense. But we could also include 2 exercises? One for dumping and one for adding/creating/updating?

@libcce
Copy link
Contributor Author

libcce commented May 18, 2021

It's the exercise on dumping that I'm not sure about. We have to consider the overall time to teach the lesson. So just thinking of this when I suggest that maybe it can just be a highlight?

@mimkes
Copy link
Contributor

mimkes commented May 19, 2021

Yes, we could dump the dumping exercise. Anyway, I am not sure how to use .dump with the DB browser. The browser offers importing and exporting, but I am not sure how to use .dump .

@jyssy
Copy link
Contributor

jyssy commented Aug 18, 2021

@mimkes, @libcce We could also add the .dump or backing up as an FYI, or something if we don't want to add it to the lesson (because of timing). thoughts?

@mimkes
Copy link
Contributor

mimkes commented Aug 19, 2021

An FYI sounds like a good idea to me.

@jyssy jyssy self-assigned this Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants