forked from amazingfate/loongoffice
05d7382940
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
Java database engine from [http://hsqldb.org/]. Default database format for OpenOffice.org. Also used in LibreOffice but shall be replaced as default by SQLite.