We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The create portion of upsert does not work if an id is supplied in the data argument.
data
Sample upsert call
MyModel.upsert({ myId: 'some-value', otherData: 'something' });
Model definition
{ "name": "MyModel", "base": "PersistedModel", "idInjection": true, "options": { "validateUpsert": true }, "properties": { "myId": { "type": "string", "id": true, "required": true }, "otherData": { "type": "string" } }, "validations": [], "relations": {}, "acls": [], "methods": {} }
Document should be created if not found by id.
404 is thrown. Received error message: No instance with id df97cbcd-8246-49ee-9354-599e8fe64e2f found for MyModel
No instance with id df97cbcd-8246-49ee-9354-599e8fe64e2f found for MyModel
This commit d5dd8c7 caused the upsert to break.
loopback-connector-cloudant: 1.2.2 Node Version: 6.0.0
The text was updated successfully, but these errors were encountered:
fix conflict
d5dd8c7
Closing since #129 merged
Sorry, something went wrong.
jannyHou
No branches or pull requests
Bug or feature request
Description of feature (or steps to reproduce if bug)
The create portion of upsert does not work if an id is supplied in the
data
argument.Sample upsert call
Model definition
Link to sample repo to reproduce issue (if bug)
Expected result
Document should be created if not found by id.
Actual result (if bug)
404 is thrown. Received error message:
No instance with id df97cbcd-8246-49ee-9354-599e8fe64e2f found for MyModel
Cause
This commit d5dd8c7 caused the upsert to break.
Additional information (Node.js version, LoopBack version, etc)
loopback-connector-cloudant: 1.2.2
Node Version: 6.0.0
The text was updated successfully, but these errors were encountered: