Split data dictionary into separate markdown tables by SQL table

[dmolesUC]

If this pull request addresses an open issue on the repository, please add 'Closes #NN' below, where NN is the issue number.

Closes #384.

Please briefly summarise the changes made in the pull request, and the reason(s) for making these changes.

• Separates the data dictionary into three separate Markdown tables (one per SQL table), so as not to confuse students when they first import only the surveys table
• Rearranges fields into the order they appear in the DB Browser for SQL Lite interface (= the order of columns in the CSV, which also becomes the SQL declaration order), so it's easier for students to read down the table as they set data types

If any relevant discussions have taken place elsewhere, please provide links to these.

See #384.

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/datacarpentry/sql-ecology-lesson/compare/md-outputs..md-outputs-PR-386

The following changes were observed in the rendered markdown documents:

 00-sql-introduction.md | 46 ++++++++++++++++++++++++++++++----------------
 md5sum.txt             |  2 +-
 2 files changed, 31 insertions(+), 17 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2026-03-31 11:28:35 +0000