-
-
Notifications
You must be signed in to change notification settings - Fork 141
bug: UNION clause return error: UNION of non-matching columns (column no 0) #1870
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
Closed
2 of 3 tasks
Labels
A-bug
Something isn't working
Milestone
Comments
既然已经成功的解决了客户POC的问题 #1873 , 没有理由不顺带着解决这个类似的问题 |
但是这个问题的场景又有所不同 (gdb) p type2
$3 = {
type = Tianmu::common::ColumnType::NUM,
unsigned_flag_ = false,
precision = 17,
scale = 10,
internal_size = 8,
display_size = 19,
collation = {
collation = 0x446fae0 <my_charset_latin1>,
derivation = DERIVATION_NUMERIC,
repertoire = 3
},
fmt = Tianmu::common::PackFmt::DEFAULT,
flag = std::bitset
}
|
decimal在mysql官方的文档做下备忘录 https://dev.mysql.com/doc/refman/5.7/en/fixed-point-types.html |
问题就在乎,这个精度,是写了魔数不做支持,但是为什么能创建表属性成功?还能插入数据? d2 DECIMAL(17,10)
|
所以根据以上的逻辑,在临时表中做和物理表相同的逻辑对策 |
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you read the Contributing Guidelines on issues?
Please confirm if bug report does NOT exists already ?
Describe the problem
If the fields use other data type, the same union query is supported, so this problem should be a bug !
Expected behavior
No response
How To Reproduce
No response
Environment
Are you interested in submitting a PR to solve the problem?
The text was updated successfully, but these errors were encountered: