explaingit

anndreloopez012/campuslands-dev-sql

21ShellAudience · developerComplexity · 1/5Setup · easy

TLDR

A Spanish-language teaching repository of structured SQL exercises that walk students through designing, building, and querying relational databases using SQLite and Git branching workflows.

Mindmap

mindmap
  root((campuslands-dev-sql))
    Learning Path
      Design tables and relations
      Write SQL schema
      Insert and query data
    Structure
      ejercicios folder
      Template per exercise
      resoluciones submissions
    Git Workflow
      Protected main and dev
      Branch per exercise
      Pre-commit hook guard
    Tools
      SQLite local only
      Git
      Draw.io or Mermaid
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Work through structured SQL exercises to learn how to design and build relational database schemas from scratch.

USE CASE 2

Practice the full student workflow: copy a template, write SQL, commit on a feature branch, and merge back to dev.

USE CASE 3

Use as a course template to run SQL assignments for a class with Git-based submission and protected branch rules.

Tech stack

SQLSQLiteShell

Getting it running

Difficulty · easy Time to first run · 30min

Instructions are in Spanish, non-Spanish readers will need to translate the README before starting.

No license information was mentioned in the explanation.

In plain English

This is a structured collection of SQL exercises, written in Spanish, aimed at students learning how to design and work with relational databases. The exercises walk through the full cycle: analyzing what a database needs to store, identifying the tables and relationships, writing the SQL to build those tables, inserting sample data, and then querying it back out. It is a teaching repository rather than a finished application. The folder layout keeps things tidy. Each exercise lives under an ejercicios/ directory with its own instructions and a template folder containing separate files for table definitions, data inserts, and query scripts. Students copy that template into a resoluciones/ folder, fill in the SQL, and submit their work through Git. The database engine used is SQLite, which runs locally without needing a server. The repository enforces a branching discipline that mirrors real team workflows. There are two protected branches: main for stable, approved work, and dev as the base for all new work. Students create a fresh branch for each exercise, make small focused commits, and merge back into dev. A pre-commit hook blocks accidental direct commits to the protected branches. Instructors decide when changes are promoted from dev to main. The tooling needed is minimal: Git, SQLite 3, and optionally a diagram tool such as Draw.io or Mermaid for drawing entity-relationship diagrams when exercises require them. File naming follows simple conventions: lowercase with hyphens for folders, .sql extension for all SQL files, and solutions must run cleanly on an empty database from scratch. The README is in Spanish, so readers who do not speak Spanish will need a translation for the exercise instructions, though the folder structure and SQL files themselves are language-independent.

Copy-paste prompts

Prompt 1
I'm learning SQL and want to practice with campuslands-dev-sql. Walk me through copying the exercise template into resoluciones, writing the table definitions, and submitting via a Git branch.
Prompt 2
Show me the SQLite commands to run the schema and insert scripts in one of the campuslands-dev-sql exercises so I can verify my tables look correct.
Prompt 3
I'm an instructor. How do I fork campuslands-dev-sql, add a new exercise with its own template folder, and configure the pre-commit hook to protect main and dev branches?
Open on GitHub → Explain another repo

← anndreloopez012 on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.