Why CRUD operations through models in Ruby on Rails? - Purpose & Use Cases

The Big Idea

What if you could manage your app's data with just a few simple commands instead of complex SQL?

The Scenario

Imagine building a web app where you manually write SQL queries everywhere to create, read, update, and delete data.

Every time you want to change a user's info, you write raw SQL in your controller or view.

The Problem

Writing SQL manually is slow and easy to mess up.

You might forget to sanitize inputs, causing security holes.

It's hard to keep track of all queries scattered across your code.

The Solution

Rails models let you handle data with simple Ruby methods instead of raw SQL.

This keeps your code clean, safe, and easy to maintain.

Before vs After

✗ Before

User.connection.execute("INSERT INTO users (name, email) VALUES ('Alice', '[e-mail]')")

✓ After

User.create(name: 'Alice', email: '[e-mail]')

What It Enables

You can focus on your app's logic while Rails handles database details safely and efficiently.

Real Life Example

When a user signs up, you just call User.create with their info instead of writing SQL queries yourself.

Key Takeaways

Manual SQL is error-prone and scattered.

Rails models provide simple methods for CRUD operations.

This makes your code safer, cleaner, and easier to work with.