-
Zolnai Tamás yazdı
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
05d73829
Adı |
Son kayıt (commit)
|
Son güncelleme |
---|---|---|
.. | ||
fdo36824.patch | ||
i103528.patch | ||
i104901.patch | ||
i96823.patch | ||
i97032.patch | ||
jdbc-4.1.patch | ||
limit_as_table_alias.patch |