Implement pointer types in postgres. #2086
Merged
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
ghost
added
the
|
@drew-gross updated the pull request. |
|
Just merged, you still have conflicts, maybe because of the squash merge |
|
Probably yea. Will rebase. |
|
@drew-gross updated the pull request. |
|
Waiting for travis but LGTM |
Current coverage is 89.75%@@ master #2086 diff @@
==========================================
Files 93 93
Lines 6764 6767 +3
Methods 1191 1190 -1
Messages 0 0
Branches 1430 1431 +1
==========================================
Hits 6074 6074
- Misses 690 693 +3
Partials 0 0
|
|
@drew-gross updated the pull request. |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Store pointers as strings because in Parse you can create pointers to objects that don't exist (and even classes that don't exist)
Based on #2081, merge that first then update this branch on top of that.