In the 6 rules for type resolution, rule 5 says "select the first non-unknown input type as candidate, and consider if other non-unknown types can be implicitly converted." ... should there not be a new rule, something like considering if the unknown types can be converted, then notice that a long string can't be converted to a char, because it won't fit? And then fail with an interesting error?
Do you have an example demonstrating this new rule? I'm doubting this resolution logic goes into that much depth regarding the semantics of each type. It is implied that even if an implicit cast exists from type A to type B that actual values of type A may fail during the casting process to make them type B. That would be the interesting error you'd end up seeing - but from the type casting/input system, not the type resolution one.
From:
Chris BSomething Date: Subject:
Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
✖
By continuing to browse this website, you agree to the use of cookies. Go to Privacy Policy.
