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
ALTER COLUMN TYPE to lower integer range (Ex int8 to int2) should fail #54844
Comments
Hi @vy-ton, please add a C-ategory label to your issue. Check out the label system docs. While you're here, please consider adding an A- label to help keep our repository tidy. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan. |
hehe, yeah it's broken because we don't validate precisions on casts....
|
cc @solongordon i think this may be a release blocker as it puts invalid data into the table. |
Hi. In what version it will be enable once again? |
@z0mb1ek This will be enabled in 21.1. You can check out the latest 21.1 beta release or wait for GA release which is coming very soon |
Steps to reproduce
Desired behavior
Our docs indicate that only increasing precision is allowed and that the existing data must remain valid. This
ALTER COLUMN TYPE
violates that.I realized I was looking at 20.1 docs, but there's no mention in 20.2 docs that this would be valid.
In PG,
The text was updated successfully, but these errors were encountered: