diff options
| author | Zolnai Tamás <zolnaitamas2000@gmail.com> | 2013-06-13 10:40:31 +0200 |
|---|---|---|
| committer | Zolnai Tamás <zolnaitamas2000@gmail.com> | 2013-06-14 09:45:36 +0200 |
| commit | 05d738294025b4a26e7cc3c6180e10ff784555e2 (patch) | |
| tree | 4eff53cfb09f67c95887bfbbb5d26fc527837c27 /hsqldb/UnpackedTarball_hsqldb.mk | |
| parent | cppcheck: fix duplicateExpression (diff) | |
| download | core-05d738294025b4a26e7cc3c6180e10ff784555e2.tar.gz core-05d738294025b4a26e7cc3c6180e10ff784555e2.zip | |
hsqldb does not support "select * from t limit n"
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
Diffstat (limited to 'hsqldb/UnpackedTarball_hsqldb.mk')
| -rw-r--r-- | hsqldb/UnpackedTarball_hsqldb.mk | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/hsqldb/UnpackedTarball_hsqldb.mk b/hsqldb/UnpackedTarball_hsqldb.mk index af7883427e10..271f692b9af0 100644 --- a/hsqldb/UnpackedTarball_hsqldb.mk +++ b/hsqldb/UnpackedTarball_hsqldb.mk @@ -23,6 +23,7 @@ $(eval $(call gb_UnpackedTarball_add_patches,hsqldb,\ hsqldb/patches/i103528.patch \ hsqldb/patches/i104901.patch \ hsqldb/patches/fdo36824.patch \ + hsqldb/patches/limit_as_table_alias.patch \ $(if $(filter YES,$(HSQLDB_USE_JDBC_4_1)),\ hsqldb/patches/jdbc-4.1.patch \ ) \ |