)]}'
{
  "commit": "321697cec58bb2ceef23d80d49a732d90d4a460f",
  "tree": "e0f8fc6fd60f921b6b7a268119f6c9c6f0459ae9",
  "parents": [
    "2c0643d12c5c087e2d55fd24074307adb3f3e004"
  ],
  "author": {
    "name": "David Ostrovsky",
    "email": "david@ostrovsky.org",
    "time": "Fri Jul 04 01:23:59 2014 +0200"
  },
  "committer": {
    "name": "David Pursehouse",
    "email": "david.pursehouse@sonymobile.com",
    "time": "Fri Jul 04 09:27:45 2014 +0900"
  },
  "message": "Only bind LIMIT variable in SQL when dialect supports it\n\nJdbc dialect may claim not to support LIMIT construct by overriding\nselectHasLimit() method and returning false.\n\nWhen this is the case, then the query model doesn\u0027t generate LIMIT ?\nconstruct.  Since Ie18898242 however limit variable is always bound\ninto prepare statement, i. e. by calling setInt(1, 5) on it. But this\nobviously cannot work as select statement doesn\u0027t include any bind\nvariables. As the consequence it fails with:\n\n  java.sql.SQLException: Invalid column index\n\nRectify it by only binding the variables in the LIMIT construct, when\nJdbc dialect claims to support it.  Currently all dialects support it,\nwith one exception: Oracle.\n\nChange-Id: Ibea3e71ea8df79bb238d4ff21c4c1b9748439d2a\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7cba532898a2d45103e29be90ea6db29de4ec12b",
      "old_mode": 33188,
      "old_path": "src/main/java/com/google/gwtorm/jdbc/AccessGen.java",
      "new_id": "3066f735610d6009e45538444a786097323fc6e9",
      "new_mode": 33188,
      "new_path": "src/main/java/com/google/gwtorm/jdbc/AccessGen.java"
    }
  ]
}