This repository was archived by the owner on Jul 25, 2018. It is now read-only.
Use json for occurrences column #110
Open
Conversation
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
|
Stalled for now, we need the data from @MusicConnectionMachine/group-2 first in the DB |
Contributor
|
@pfent its in now - whats next? |
pfent
approved these changes
Apr 23, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
This changes the datatype of the occurrences column from
TEXTtoJSON.Example data:
{"term":"saxophone","positions":[226,241,257,274,293,320,622,1759,1864,1992,2085,2201,2287,2401,9298,9488]}We might want to use JSONB instead which is a binary format, allows quicker queries but might take up more space. Also I'm not sure if it is possible to cast our current text data to JSONB.