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
This issue is really easy to recreate and explain. It doesn't even need a template :)
Parse never had a way to create unique columns. So they only way to make sure there are no duplicates is use the beforeSave hook to check if the object already exists. If it already exists return response.error if not response.success.
This works great if you independently save an object. But when you use saveAll this fails
It tries to save all but when one is a duplicate it will throw back a error ofcourse because of the beforeSave hook and the method skips the rest of the objects...
Is there no way around this ? or do we then just have to use save each object independently ? Doesnt this use more connections ?
The text was updated successfully, but these errors were encountered:
This appears to be a usage question and not an issue with Parse Server. I am closing this out as we're trying to cut down on the number of non-issues here on GitHub.
You may use Server Fault for questions about managing Parse Server.
For code-level and/or implementation-related questions or technical support, please refer to Stack Overflow.
This issue is really easy to recreate and explain. It doesn't even need a template :)
Parse never had a way to create unique columns. So they only way to make sure there are no duplicates is use the beforeSave hook to check if the object already exists. If it already exists return response.error if not response.success.
This works great if you independently save an object. But when you use saveAll this fails
It tries to save all but when one is a duplicate it will throw back a error ofcourse because of the beforeSave hook and the method skips the rest of the objects...
Is there no way around this ? or do we then just have to use save each object independently ? Doesnt this use more connections ?
The text was updated successfully, but these errors were encountered: