Day 79 of Learning MERN Stack

Hello Dev Community! 👋

It is officially Day 79 of my 100-day full-stack and database engineering streak! Yesterday, I locked down structural table relationships using primary and foreign keys. Today, I shifted focus to internal data integrity, custom conditional filtering, and database analytics by mastering: CHECK Constraints, the WHERE Clause, Comparison Operators, and Aggregation Functions! 📊🔥

To build truly resilient backend systems, you cannot just fetch raw data pools blindly; you must compute metrics and enforce business rules straight inside your storage engine. Today, I did exactly that!

---

🧠 The 4 Pillars I Coded on Day 79

As showcased inside my query scripts across "Screenshot (178).png" and "Screenshot (180).png", today's execution upgrades the database layer with major capabilities:

1. Defensive Data Guardrails (CHECK Constraint)

Instead of relying strictly on backend or frontend validation logic, I implemented structural rule enforcement directly into the schema. By adding CHECK (age >= 18), the database instantly drops any rogue insert queries attempting to write underage data points into the tables.

2. Granular Selection Logic (WHERE & Comparison Operators)

I explored the mechanics of data targeting using the WHERE clause matched with structural operators (>, <, =, !=, AND, OR). This allows me to segment and slice tabular rows based on multiple intersecting conditions (e.g., pulling profiles with specific salaries or localized age metrics).

3. Native Data Summary Computations (Aggregation Functions)

As written inside my testing logs in "Screenshot (180).png", I stopped pulling large data arrays to process arithmetic inside JavaScript arrays. Instead, I let the database optimize computations natively using SQL's core mathematical aggregators:

• COUNT() — Tracking the exact frequency volume of matching rows.
• SUM() / AVG() — Calculating automated balance sheets and statistical medians.
• MIN() / MAX() — Instantly auditing boundaries across financial or numerical columns.

---

🛠️ Operational Look at the Daily Query Architecture

Here is a conceptual view of how these independent features work together inside a unified structural database context:

sql
-- Enforcing strict column rule validation
CREATE TABLE user_registry (
    id INT PRIMARY KEY,
    name VARCHAR(50),
    age INT,
    salary INT,
    CONSTRAINT chk_user_age CHECK (age >= 18)
);

-- Advanced conditional rows query extraction
SELECT name, salary 
FROM user_registry 
WHERE age > 21 AND salary >= 35000;

-- Running real-time internal analytics queries
SELECT 
    COUNT(*) AS total_staff,
    AVG(salary) AS median_payout,
    MAX(salary) AS peak_earnings
FROM user_registry;