tree e0f8fc6fd60f921b6b7a268119f6c9c6f0459ae9
parent 2c0643d12c5c087e2d55fd24074307adb3f3e004
author David Ostrovsky <david@ostrovsky.org> 1404429839 +0200
committer David Pursehouse <david.pursehouse@sonymobile.com> 1404433665 +0900

Only bind LIMIT variable in SQL when dialect supports it

Jdbc dialect may claim not to support LIMIT construct by overriding
selectHasLimit() method and returning false.

When this is the case, then the query model doesn't generate LIMIT ?
construct.  Since Ie18898242 however limit variable is always bound
into prepare statement, i. e. by calling setInt(1, 5) on it. But this
obviously cannot work as select statement doesn't include any bind
variables. As the consequence it fails with:

  java.sql.SQLException: Invalid column index

Rectify it by only binding the variables in the LIMIT construct, when
Jdbc dialect claims to support it.  Currently all dialects support it,
with one exception: Oracle.

Change-Id: Ibea3e71ea8df79bb238d4ff21c4c1b9748439d2a