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.

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

Support assign DEFAULT in ON DUPLICATE KEY UPDATE statement #13071

Closed
Deardrops opened this issue Nov 1, 2019 · 0 comments · Fixed by #13168
Closed

Support assign DEFAULT in ON DUPLICATE KEY UPDATE statement #13071

Deardrops opened this issue Nov 1, 2019 · 0 comments · Fixed by #13168
Assignees

Comments

@Deardrops
Copy link
Contributor

Deardrops commented Nov 1, 2019

Bug Report

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 (a int unique, 
	b int generated always as (-a) virtual,
	c int generated always as (-a) stored);


insert into t1 values (1,default,default);

insert into t1 values (1,default,default) on duplicate key update a=2, b=default;
  1. What did you expect to see?
Query OK, 1 row affected (0.01 sec)
  1. What did you see instead?
ERROR 3105 (HY000): The value specified for generated column 'b' in table 't1' is not allowed.
  1. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?
Release Version: v4.0.0-alpha-693-gada724a2a
@Deardrops Deardrops added type/bug The issue is confirmed as a bug. type/compatibility and removed type/bug The issue is confirmed as a bug. labels Nov 1, 2019
@Deardrops Deardrops self-assigned this Nov 1, 2019
@Deardrops Deardrops changed the title Support use on duplicate key update b=default in generated columns Support use on duplicate key update b=default on generated columns Nov 5, 2019
@Deardrops Deardrops changed the title Support use on duplicate key update b=default on generated columns planner: Support assign DEFAULT to generated column in on duplicate key update statement Nov 6, 2019
@Deardrops Deardrops changed the title planner: Support assign DEFAULT to generated column in on duplicate key update statement Support assign DEFAULT to generated column in on duplicate key update statement Nov 6, 2019
@Deardrops Deardrops changed the title Support assign DEFAULT to generated column in on duplicate key update statement Support assign DEFAULT in on duplicate key update statement Nov 12, 2019
@Deardrops Deardrops changed the title Support assign DEFAULT in on duplicate key update statement Support assign DEFAULT in ON DUPLICATE KEY UPDATE statement Nov 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant