-
Notifications
You must be signed in to change notification settings - Fork 52
Fix Decimal type when precision and scale are unspecified #197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
require "cases/helper_cockroachdb" | ||
|
||
# Load dependencies from ActiveRecord test suite | ||
require "support/schema_dumping_helper" | ||
|
||
module CockroachDB | ||
class PostgresqlNumberTest < ActiveRecord::PostgreSQLTestCase | ||
include SchemaDumpingHelper | ||
|
||
class PostgresqlNumber < ActiveRecord::Base; end | ||
|
||
setup do | ||
@connection = ActiveRecord::Base.connection | ||
@connection.create_table("postgresql_numbers", force: true) do |t| | ||
t.decimal 'decimal_default' | ||
end | ||
end | ||
|
||
teardown do | ||
@connection.drop_table "postgresql_decimals", if_exists: true | ||
end | ||
|
||
def test_decimal_values | ||
record = PostgresqlNumber.new(decimal_default: 111.222) | ||
assert_equal record.decimal_default, 111.222 | ||
end | ||
end | ||
end |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this comment should still be here since ideally we wouldn't need this conditional and
OID::Decimal
would properly handle the case where precision is defined, but the scale is not.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I removed it because it's not in the original rails code and the new logic is much closer to the original logic in rails.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, you're right. I think issue #178 can be closed since this handles the case described in that issue (
DECIMAL
where only precision is specified).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, can you add this back in now? I'm going to add to that issue to reflect the problem we saw with precision being improperly handled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I verified it does the same behavior in vanilla activerecord.