Skip to content
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

fix: column type conflicts #435

Merged
merged 1 commit into from
Oct 21, 2024
Merged

fix: column type conflicts #435

merged 1 commit into from
Oct 21, 2024

Conversation

serprex
Copy link
Member

@serprex serprex commented Oct 17, 2024

  1. a,b=b,a would leave b==c, always returning false
  2. Decimal256 should not conflict with Decimal(76, 38)
  3. propagate conflicts to inner types for Nullable/Array/LowCardinality

Checklist

  • Unit and integration tests covering the common scenarios were added

@serprex serprex requested review from jkaflik and ernado October 17, 2024 20:28
@serprex serprex force-pushed the fix-conflicts branch 2 times, most recently from 944bc8d to e13d46d Compare October 17, 2024 20:34
@serprex serprex changed the title fix: ColumnType.Conflicts for Decimal/Nullable/Array/LowCardinality fix: column type conflicts Oct 17, 2024
1. `a,b=b,a` would leave `b==c`, always returning false
2. Decimal256 should not conflict with Decimal(76, 38)
3. propagate conflicts to inner types for Nullable/Array/LowCardinality
@ernado ernado merged commit abd6ab7 into main Oct 21, 2024
25 checks passed
@ernado ernado deleted the fix-conflicts branch October 21, 2024 10:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants