Exam 200-301 topic 1 question 777 discussion

POST GET DELETE PATCH Wouldn't "patch" be the "safer" option, since you are just updating one thing in a database and not the complete database? Put could wipe the entries you are not modifying? https://rapidapi.com/blog/put-vs-patch/ Feel free to correct me if i got it wrong.

PUT The single-resource equivalent of POST is PUT, which updates a resource by replacing its content entirely. As a RESTful API HTTP method, PUT is the most common way to update resource information. It's possible to create a resource with a PUT method, but this approach carries the risk of creating resources by accident, as noted above. If PUT is applied to a collection of resources, the entire resource collection gets replaced, which usually isn't the intention. PATCH PATCH is another HTTP method used to update resources. As opposed to replacing resources, like the PUT method does, PATCH only modifies resource contents. As a general rule, these modifications should be expressed in a standard format like JSON or XML. Much like in PUT, it's poor practice to specifically apply PATCH methods to a whole resource collection -- that is, unless you truly intend to update every resource it contains.

In REST APIs, "PUT" and "PATCH" are both HTTP methods used to update resources, but they differ in their semantics: 1. **PUT**: This method is used to completely replace a resource or create it if it doesn't exist. When you make a PUT request to a resource endpoint, you send the complete representation of the resource you want to update. If the resource already exists, it will be completely replaced with the new representation provided in the request. If the resource doesn't exist, it will be created. 2. **PATCH**: PATCH, on the other hand, is used to partially update a resource. With PATCH, you send only the changes that need to be applied to the resource, rather than the entire representation. This allows for more efficient updates, especially when dealing with large resources where sending the entire representation would be impractical. In summary, PUT is used for full updates or creation of resources, while PATCH is used for partial updates.

I will choose 'PUT'. Both `PUT` and `PATCH` methods can be used to update an entry in the database using a REST API, but they are used in slightly different scenarios: - `PUT` is used when you want to **replace** an entire resource. For example, if you have a user object with fields like `name`, `email`, and `password`, and you want to update all these fields, you would use the `PUT` method. - `PATCH`, on the other hand, is used when you want to **update** only certain fields of a resource. For example, if you only want to update the `email` field of the user object mentioned above, you would use the `PATCH` method. So, if you're updating an entire entry, you'd typically use `PUT`. If you're updating only certain fields of an entry, you'd use `PATCH`.