Diffrence between Put and Patch

PUT: Imagine you're replacing the entire contents of a document. With PUT, you send the complete updated version of the data to the server. It's like rewriting the whole document.


PATCH: This is like editing specific parts of a document. You only send the changes you want to make, leaving the rest untouched.


Example:


Let's say you have a user profile with information like name, email, and phone number.


PUT: If you want to update the entire profile with new data for all fields (name, email, phone), you'd use PUT and send the complete new user information.

PATCH: If you only want to change the user's email address, you'd use PATCH and send just the updated email information.

Here's the key difference:


PUT: Replaces the entire resource.

PATCH: Updates specific parts of a resource. 

Comments

Post a Comment

Popular posts from this blog

Add Css And Js Files on Specific Page In laravel

  1. Using Blade Layout Sections: Laravel's Blade templating engine provides a powerful way to manage layouts and include specific content on different pages. Here's how to achieve this: a. Base Layout ( layouts/app.blade.php ): <!DOCTYPE html> <html> <head> <title>My Website</title> @yield('page-css') <link rel="stylesheet" href="{{ asset('css/app.css') }}"> </head> <body> @include('partials.header') <main>@yield('content')</main> @include('partials.footer') @yield('page-js') <script src="{{ asset('js/app.js') }}"></script> </body> </html> b. Specific Page View ( views/home.blade.php ): @extends('layouts.app') @section('content')   @endsection @section('page-css')   <link rel="stylesheet" href="{{ asset('css/home.css') }}">  @endsection @se...
Read more

Xpendy Pending

 1) Experiment Xpendy | E-mail domain suggestion Done 2) Xpendy Experiment | Change red error color to orange Done 3) My Xpendy | Implementation of credit card payments in ChargeBee 4) My Xpendy | Briefing split audience Mailchimp 5) Xpendy | Customers can only do one conversion from oneclick email Done 6) Xpendy | Send letters by e-mail Done 7)My Xpendy | Optimization of IT and ES Done 8)Experiment Xpendy | XPE-0110 - Form field bigger than letter  pending 9)Xpendy | Implement experiment 100% on live website NL Done 10)Xpendy | Implement XPE-0112 experiment for AT website Done 11)Xpendy | Third mail - proof of arrival implementation Pending 12)Xpendy | Adding code for experimentation tool in progress 13)Xpendy | Automating SEO content + Add Button for changes & category error - feedback  in progress 14)Xpendy | Split testing collection mail NL via Mandrill Pending https://docs.google.com/spreadsheets/d/1C2NsDA72aeaIYDE7KNyTopcUernHWAvVGCocEzksKhQ/edit?usp=sharing 15)...
Read more

Laravel Join with two coloums

 <?php namespace App\Http\Controllers; use App\Models\User; use Illuminate\Support\Facades\DB; class UserController extends Controller {     public function getUserOrders()     {         // Using Eloquent with inner join (default)         $usersWithOrders = User::join('orders', function ($join) {             $join->on('users.id', '=', 'orders.user_id');             $join->on('users.email', '=', 'orders.email'); // Additional join condition         })->get();         // Using DB facade with a more complex join (optional)         $complexJoin = DB::table('users')             ->select('users.id', 'users.name', 'orders.id as order_id', 'orders.product_id', 'orders.created_at')             ->join('orders', function ($join) {   ...
Read more