You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
harsh-kukreja opened this issue
Dec 21, 2019
· 6 comments
Assignees
Labels
BugA problem or regression with an existing featurehas-prAn issue that has a pull request pending that may fix this issue. The pull request may be incomplete
Whenever i create a field with timestamp suppose the field is null initially then a double click on the cell and use the Timestamp() to get the current timestamp the method takes the date correct but always gives the time as 00:00:00.000000
To Reproduce
Steps to reproduce the behavior:
Create any table with a tuple with timestamp type
Initially do not insert any value in it keep it null
Insert a new row then double click and edit and write Timestamp()
You can see it will take the date perfectly but not the time
Expected behavior
It should take both date and time which is currently going on
Screenshots
Server configuration
phpMyAdmin version:4.9.2
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
BugA problem or regression with an existing featurehas-prAn issue that has a pull request pending that may fix this issue. The pull request may be incomplete
Describe the bug
Whenever i create a field with timestamp suppose the field is null initially then a double click on the cell and use the Timestamp() to get the current timestamp the method takes the date correct but always gives the time as 00:00:00.000000
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should take both date and time which is currently going on
Screenshots
Server configuration
The text was updated successfully, but these errors were encountered: