Age | Commit message (Collapse) | Author | Files | Lines |
|
If limit clause follow from clause directly than the statement
parser of hsqldb parses "LIMIT" token like a table alias and
that's why the next number is unexpected.
The problem was that the limit token was not added to a "keyword"
vector in which parser search while working with form clause.
If the algorithm find a keyword after table names than it
knows it is the end of the form clause. That's why it
worked with any other keywords like "ORDER_BY",
"WHERE", "GROUP BY" and so on.
Change-Id: Iacd3ea3493c85eb0f2579aaad6903537ac65d25a
(cherry picked from commit 05d738294025b4a26e7cc3c6180e10ff784555e2)
|
|
Change-Id: I9215fbfaf5c2e5d40e7257cd52d8d9544599ea63
|
|
Change-Id: I16edd2d6f0c7fbf2a7686e5adc43b1848902b957
|
|
Change-Id: I75e4566509d1851e7405d1738ffeaf58261233ea
|
|
Change-Id: I35bf8094c9dcf0f70e59c1304ab5a6800393fa29
|