Timeline for column values do not return properly when column name called out specifically in select statement
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 24, 2016 at 22:34 | answer | added | Ezequiel Tolnay | timeline score: 0 | |
| Apr 24, 2016 at 21:37 | comment | added | Rick James | @ZiggyCrueltyfreeZeitgeister - write that as an Answer. | |
| Apr 22, 2016 at 0:38 | comment | added | Ezequiel Tolnay | You'll always have to use backticks enclosing utc_date to make it work. But it is a recipe for trouble, you may want to consider renaming the column. | |
| Apr 21, 2016 at 21:20 | comment | added | MaQleod | The thing is that it USED to work fine, until I ran that one query with curdate(). | |
| Apr 21, 2016 at 21:02 | comment | added | Jonathan Fite |
utc_date is a reserved function. My guess is that it's interpreting it literally and giving you the current utc_date. Try addressing the column surrounded in accent marks. SELECT * FROM shift WHERE utc_date LIKE '%2016%'
|
|
| Apr 21, 2016 at 20:19 | history | asked | MaQleod | CC BY-SA 3.0 |