Attain expertise in SpringMVC

@GetMapping: This annotation is used to map HTTP GET requests onto specific handler methods in Spring MVC controllers. It is used to handle GET requests for a specific URI (Uniform Resource Identifier).

it is like saying "When someone wants to view some information (like a list of books), use this method to get that information and show it to them." It's for retrieving data.

@PostMapping: This annotation is used to map HTTP POST requests onto specific handler methods in Spring MVC controllers. It is used to handle POST requests for a specific URI.

This one is for sending data to the server to create something new. Imagine you're adding a new book to a library. When you fill out a form online and hit "submit," that's a POST request. This annotation tells Spring Boot to use a specific method to handle creating new data.

@PutMapping: This annotation is used to map HTTP PUT requests onto specific handler methods in Spring MVC controllers. It is used to handle PUT requests for a specific URI.

it is used for updating existing data. Let's say you want to change the details of a book in the library's database. You'd use a PUT request to send the updated information to the server. This annotation tells Spring Boot which method to use to update that data.

@DeleteMapping: This annotation is used to map HTTP DELETE requests onto specific handler methods in Spring MVC controllers. It is used to handle DELETE requests for a specific URI.

this one is for deleting data. If you want to remove a book from the library's database, you'd send a DELETE request. This annotation directs Spring Boot to use a specific method to handle deleting that data.

summary:@GetMapping: Retrieve data.
@PostMapping: Create new data.
@PutMapping: Update existing data.
@DeleteMapping: Delete data.

Comments

Understanding SQL in MySQL: From DDL to DCL

📦 MySQL is a widely-used relational database management system (RDBMS) that uses Structured Query Language (SQL) to manage and manipulate data. SQL is divided into several categories, each serving a specific purpose: DDL, DML, DQL, TCL, and DCL. 1. Data Definition Language (DDL) DDL commands are used to define and manage database structures such as tables, indexes, and schemas. The main DDL commands include CREATE, ALTER, DROP, and TRUNCATE. ⭐ CREATE: This command creates a new database object. CREATE TABLE students ( id INT PRIMARY KEY, name VARCHAR(100), age INT ); ⭐ ALTER : This command modifies an existing database object. ALTER TABLE students ADD COLUMN email VARCHAR(100); ⭐ DROP : This command deletes an existing database object. DROP TABLE students; ⭐ TRUNCATE : This command removes all records from a table without deleting the table itself. TRUNCATE TABLE students;

SQL vs NoSQL

📦 SQL vs NoSQL 📑 🌟 SQL (Structured Query Language) :Organized and follows strict rules (like books on specific shelves). ▶ Think of it like a well-organized library where every book is placed neatly on a specific shelf. ▶ The shelves are labeled with categories, and each book has a specific spot. ▶ You have a strict rule about how books are organized, and every book follows this rule. 🌟 NoSQL (Not Only SQL) : Flexible and can be organized in different ways (like books on shelves, in piles, or in boxes). ▶ Now, imagine a different kind of library where books are placed in different ways. ▶ Some books are on shelves, some are in piles, and some are in boxes. ▶ There are no strict rules about where to put the books. You can organize them in whatever way makes sense at the time. 🎨 Use Cases: 🎢 SQL: Good for situations where you need to keep things very organized and follow rules, like keeping track of a catalog of books in a library. 🎡 NoSQL: Good for situations where you ne...

Logging in SpringBoot

Hey Connections 👋 Let's learn and grow together 📈 🌟 What is logging ??? ➡ loggers are like reporters for your application. They keep track of what's happening while your application runs, like noting down important events, errors, or just general information. 📩There are different Logging Levels ⤵ 🌆 Events: Loggers record events, like when someone signs in or a new feature is added. ❌ Errors: They also note down errors, like when something goes wrong or an unexpected problem occurs. ⚠ Warnings: Sometimes, they give warnings if they see something that could be a problem later, like a traffic jam forming up ahead. 👨‍💻 Debugging: And if you need to figure out why something isn't working as expected, loggers can help by showing detailed information, like a detective piecing together clues. These logging levels help developers and operators understand the severity and importance of different log messages and prioritize them accordingly when troubleshooting or monitor...

Learn Beyond Java with me

Search This Blog