Clarify node-pg's strategy for the JSON data type in Postgres #193
Conversation
This file contains 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.
Could you please mention what you think node-pg should be doing to handle the JSON data type that appeared in Postgres 9.2?
I've asked for more info here previously:
brianc/node-postgres#208 (comment)
It'd be ideal if node-pg could parse or stringify the value of the json column going out or coming into postgres. If you need a hand with it let us know (although I also said that about node-sql and we've been super busy). In the interim we need to form a strategy for handling json data using node-pg.