[MXS-3589] qc_sqlite handles current_timestamp etc. explicitly Created: 2021-06-02 Updated: 2021-06-03 Resolved: 2021-06-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | qc_sqlite |
| Affects Version/s: | 2.3, 2.4, 2.5 |
| Fix Version/s: | 2.5.13 |
| Type: | Bug | Priority: | Major |
| Reporter: | Johan Wikman | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
The sqlite3 tokenizer detects current_timestamp, current_time and current_date explicitly and returns a specific token for them. That means that if current_timestamp() is used, it will cause a parser error. That specific handling should simply be removed as that means that they will be handled like all other variables and functions are handled. |