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
I believe the error is being triggered by the uniqueValidator(). I read on stackoverflow that if one uses
findOneAndUpdate() instead then the uniqueValidator is not invoked. However when I tried this I got an
error that one cannot modify the _id of an existing entry in the database (even though the _id is the same
value as before).
Anybody else encounter this error? Please advise.
The text was updated successfully, but these errors were encountered:
Also referred to as Stack buffer overflows. This vulnerability occurs when data received by a program is written to a memory location on the stack and the allocated space is not large enough to take the whole input. If proper boundary checks are not implemented, or unsafe functions like sprintf, fgets etc. are used which don't require a destination size limit the stack memory after the target buffer may be written to, allowing an attacker to alter the normal behaviour of the program. Most modern compilers now have a secure switch which may reorder stack variables and generate extra code to protect against this type of vulnerability.
I tried the POSTMAN api to update the user's email address via the PUT request but I get the following error
saying the _id already exists:
=====================================
{
"errors": {
"_id": "is already taken"
}
}
I believe the error is being triggered by the uniqueValidator(). I read on stackoverflow that if one uses
findOneAndUpdate() instead then the uniqueValidator is not invoked. However when I tried this I got an
error that one cannot modify the _id of an existing entry in the database (even though the _id is the same
value as before).
Anybody else encounter this error? Please advise.
The text was updated successfully, but these errors were encountered: