You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Restier Swagger support for AspNetCore : PUT doesn't appears #746
we might want to make this a discussion .....
my prior reads of the OData Standards and the HTTP Verbs i personally feel that HTTP PATCH is a better match in most cases.
PUT implies that a new entity will fully replace the current entity.
i have always used HTTP PATCH
HTTP PATCH is more in line with a SQL UPDATE statement where you only need to update some parts of a current entity.
where implementing HTTP PUT would be more like a sql delete and then an insert.
Activity
DennyFiguerres commentedon Nov 29, 2023
we might want to make this a discussion .....
my prior reads of the OData Standards and the HTTP Verbs i personally feel that HTTP PATCH is a better match in most cases.
PUT implies that a new entity will fully replace the current entity.
i have always used HTTP PATCH
HTTP PATCH is more in line with a SQL UPDATE statement where you only need to update some parts of a current entity.
where implementing HTTP PUT would be more like a sql delete and then an insert.
just my thoughts at this point....