sql: fix literal integer expression typing #74090
Labels
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
T-sql-queries
SQL Queries Team
X-nostale
Marks an issue/pr that should be ignored by the stale bot
Projects
A recent change in #73762 ensures that a literal integer does not exceed the minimum or maximum value of its type. This caused a subtle regression in default expressions. The table below should be successfully created, even though the default value exceeds the columns maximum value.
Currently we type the default expression as an INT2, but to make this behavior work, I think we'll have to type the expression as an INT8.
Jira issue: CRDB-11913
The text was updated successfully, but these errors were encountered: