CUT TO:
INT. PROJECT ARCHIVE — STORYBOARD ROOM
The USER opens PostgreSQL Analytical Query Engine.
DIVAKAR DESSAI
Let's run through the shots.
CASE FILE / COMP3311 / Database Systems
PostgreSQL Analytical Query EngineRelational Analysis with SQL & PL/pgSQL
Developed SQL views and procedural PostgreSQL functions for analysing a relational dataset involving rugs, factories, materials and manufacturing locations.
01–02 / OPENING SEQUENCE
Establishing the world
01 / Establishing Shot
The Problem
A relational dataset needed to answer increasingly complex analytical questions spanning factories, products, materials, styles and locations.
02 / Wide Shot
The Context
The project progressed from declarative SQL queries into procedural database programming using PostgreSQL.
03 / CHARACTER NOTE
DIVAKAR'S ROLE
Subject
Divakar Dessai
Production
PostgreSQL Analytical Query Engine
Take
03 / Role
Role notes
DIVAKAR DESSAI
I designed SQL queries, views and stored functions that transformed relational records into reusable analytical results.
04 / CLOSE-UP
THE ENGINEERING CHALLENGE
Later queries involved relationships that were difficult to express as simple single-table operations and required careful handling of aggregation, grouping and procedural logic.
05 / TRACKING SHOT
THE APPROACH
A plan emerges.
I combined joins and aggregate SQL queries with reusable views before moving more complex parameterised operations into PL/pgSQL functions.
06 / INSERT SHOTS
KEY FEATURES
The system takes shape.
07 / DIRECTOR'S NOTES
DESIGN DECISIONS
Things we decided along the way
01
Used declarative SQL where the problem mapped naturally to relational operations.
02
Used procedural PL/pgSQL only where more complex control flow was useful.
03
Created reusable database-level abstractions instead of duplicating query logic.
design decisions
somewhere mid-build
08 / RETAKES
WHAT WENT WRONG
Naturally, not everything cooperates.
09 / FINAL SHOT
THE OUTCOME
ProblemBuildOutcome
01
Developed increasingly complex relational queries.
02
Built reusable database-side analytical functions.
03
Gained practical experience treating PostgreSQL as a programmable data layer.
10 / PRODUCTION NOTES
TECH STACK
The tools behind the scenes.
PostgreSQLSQLPL/pgSQL
11 / BEHIND THE SCENES
LINKS
FADE OUT.
USER closes the file.
One project down. A few more stories left.
DIVAKAR DESSAI
Pick another?