Closed
Conversation
2 tasks
Member
|
@Globegitter, I think the chances of this being merged to master are slim, you will probably get a more favourable audience if you PR this against |
Member
Author
|
Ok will do. |
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I know there is the current discussion going on about
findOrCreateEach(https://github.com/balderdashy/waterline/issues/931) so it might not have been the wisest choice to add a
findAndModifyEachbut I needed afindAndModifyfunctionality (see http://docs.mongodb.org/manual/reference/method/db.collection.findAndModify/) and it seemed like a good solution to put it such a way that other people can use it as well.Usage is
Model.findAndModify(search critieras, values, [options, cb]);where-as default options look like that:
I added passing unit tests as well as adapter-tests, see balderdashy/waterline-adapter-tests#47
There is something strange going on, even though the
findAndModifypasses the unit tests and works in my app (vianpm i git+https://github.com/Globegitter/waterline.git#findAndModify) the adapter-tests do not pass and throw the same error throughout:I have no idea why this happens or how to fix this. So apart from if this actually gets merged, anyone got any idea of why that could be?
Also it does not work completely in my app via
sails-postgresql, I seem to be getting this error. I am not sure if that is related to my code or tosails-postgresql.