-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
exec: integer division causes a panic #38798
Comments
I think we just need some more |
Yeah I think that's probably right. There's a separate missing feature that's kind of related which is mixed-type comparison. This is a mixed-type binary operator. I think eventually we'll need to improve the execgen code to know how to generate all of these - at the moment it's fairly hard coded to a single type. |
solongordon
added a commit
to solongordon/cockroach
that referenced
this issue
Jul 11, 2019
Since our vectorized projection and selection operators currently only handle homogeneous types, I added logic to the planner which detects mixed types and errors out. Fixes cockroachdb#38798 Release note: None
solongordon
added a commit
to solongordon/cockroach
that referenced
this issue
Jul 11, 2019
Since our vectorized projection and selection operators currently only handle homogeneous types, I added logic to the planner which detects mixed types and errors out. Fixes cockroachdb#38798 Release note: None
craig bot
pushed a commit
that referenced
this issue
Jul 11, 2019
38816: exec: bail out on mixed type expressions r=solongordon a=solongordon Since our vectorized projection and selection operators currently only handle homogeneous types, I added logic to the planner which detects mixed types and errors out. Fixes #38798 Release note: None Co-authored-by: Solon Gordon <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Vectorized execution panics when you divide an int column by an int constant, presumably because it thinks the result should be an integer but it should actually be a decimal.
The text was updated successfully, but these errors were encountered: