overview
the capstone for the database module of a two-year program. a relational schema for an art gallery, with the queries a real back office would need against it.
the focus wasn't tables for the sake of tables. it was the queries on top — the ones that make the difference between a database you can read from and a database you can run a business on.
what it covers
- schema design with foreign keys and referential integrity.
- joins — inner, left, right — with multi-table joins that retrieve related entities in a single query.
- subqueries, including correlated subqueries and
EXISTS-based filters. - aggregations with
GROUP BYandHAVING, for the reporting queries. - views for the queries that would otherwise be repeated across the codebase.
- transactions wrapping the multi-step operations that have to succeed or fail together.
why i keep it on the portfolio
sql is one of those skills that's easy to overlook on a junior cv and impossible to fake in a technical interview. the project shows i can do more than SELECT * FROM — i can model a domain, write the queries that ship with a real product, and reason about why a join is the right choice over a subquery (or the other way around).
it also pairs well with the php auth & admin platform — that project is where the sql lives in production, with prepared statements wrapping every query.
repository
the final project lives in TrabajoFinalBBDDSQL/TF SQL_Darius_Berinde/.