Skip to content
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.

Sign up for GitHub

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

Jump to bottom

wrong union select behavior #2317

Closed
tiancaiamao opened this issue Dec 23, 2016 · 0 comments · Fixed by #2471
Closed

wrong union select behavior #2317

tiancaiamao opened this issue Dec 23, 2016 · 0 comments · Fixed by #2471
Assignees
@hanfei1991
Labels
type/bug The issue is confirmed as a bug.

Comments

@tiancaiamao
Copy link
Contributor

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    If possible, provide a recipe for reproducing the error.
CREATE TABLE t1 (f1 DATE);
INSERT INTO t1 VALUES ('1978-11-26');
SELECT f1+0 FROM t1 UNION SELECT f1+0 FROM t1;
  1. What did you expect to see?
+----------+
| f1+0     |
+----------+
| 19781126 |
+----------+
  1. What did you see instead?
+----------+
| f1+0     |
+----------+
| 19781126 |
| 19781126 |
+----------+
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hanfei1991 hanfei1991

Labels
type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

executor: fix bug of union type converting. pingcap/tidb
3 participants
@ngaut @tiancaiamao @hanfei1991