Fix prepare value map to postgres #925
Merged
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.
There was an issue where if a complex value (a value having a toPostgres function defined) was passed to prepareValue from a map operation, the index of the value would be passed as an additional parameter and prevent the internal seen variable from being correctly initialized.
Rather than try and identify all usages of this and fix the individual map operations, I thought it would be better to prevent the seen variable from being accidentally tampered with.
An example of current usage that causes problems: https://github.com/brianc/node-pg-cursor/blob/master/index.js#L6