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
current_timestamp() stringified on INSERT #16892
Comments
|
Sure |
|
I can not reproduce this issue on MariaDB 10.4 or 10.5 INSERT INTO `test` (`id`, `str`, `decimal_number`, `json`, `ct`) VALUES ('2', '2', '2', '2', current_timestamp()); |
|
@williamdes, is this a manual INSERT you created, or the one, that myAdmin generated on INSERT page? The one like |
I copied the query from the box after an insert from the page |
|
https://www.youtube.com/watch?v=0_7nit6ilrI (just realized I could have used nVidia's Shadowplay or whatever, not my phone). |
Awesome! |
|
Hey @Simbiat, thanks for the video. I was able to replicate the issue and will try to fix it. |
… date field Signed-off-by: Saksham Gupta <shucon01@gmail.com>
… date field Signed-off-by: Saksham Gupta <shucon01@gmail.com> Add tests and fix condition Signed-off-by: Saksham Gupta <shucon01@gmail.com>
Fixes #16892: current_timestamp() stringified on INSERT for date field
Signed-off-by: Maurício Meneghini Fauth <mauricio@fauth.dev>
Describe the bug
When using "Insert" page on a table, which has columns with default value of
current_timestamp()this function is treated as a string value both in "Preview SQL" and when actually inserting rows.To Reproduce
Steps to reproduce the behavior:
current_timestamp()'current_timestamp()'instead ofcurrent_timestamp()Expected behavior
Function is used as is, not as a string value
Screenshots
N/A
Server configuration
Client configuration
Additional context
N/A
The text was updated successfully, but these errors were encountered: