Closed
Conversation
Contributor
|
The SQL datastores are mostly tested through the high level shared datastore specs found here -- https://github.com/8thlight/hyperion/blob/master/api/src/hyperion/dev/spec.clj. What was the reasoning for using decompose-key here instead of just taking the id? |
Author
|
Maybe I'm missing something, but it didn't work. I don't have an id in my record at that point in the code. |
Author
|
Sorry, more specifically than "didn't work", I got this kind of error: |
Contributor
|
mylesmegyesi: "the problem was a little deeper than the solution in the pull request, so I had to fix it differently." I'm closing the issue. |
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 only saw 9 tests total for the whole SQL codebase, so I'm not sure whether there's another place I should be looking to add tests for this. Thoughts?