Adding support for Array(Float64) #443
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
jwoertink
commented
Aug 21, 2020
| macro setup_db_mapping(columns, *args, **named_args) | ||
| DB.mapping({ | ||
| {% for column in columns %} | ||
| {{column[:name]}}: { | ||
| {% if column[:type].id == Float64.id %} | ||
| type: PG::Numeric, | ||
| convertor: Float64Converter, |
There was a problem hiding this comment.
This is actually misspelled which means we were never using it. Changing the spelling to converter makes the specs fail as mentioned in #437 but it turns out we actually handle the casting ourselves in the charm extensions.
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.
Fixes #382
This adds in the
Array(Float64)support with some specs and some cleanups.