Bug #7306 the server side preparedStatement error for LIMIT placeholder

Description:
I use Connector/J 3.1.5 to access the mysql database, and run the follow java code:

String sql = "select * from sometable LIMIT ?,?";
PreparedStatement stmt = conn.prepareStatement(sql);

Then the follow exception is thowed:
java.sql.SQLException: You have an error in your SQL syntax; check the manual th
at corresponds to your MySQL server version for the right syntax to use near '?,
?' at line 1
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2849)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1534)
        at com.mysql.jdbc.ServerPreparedStatement.serverPrepare(ServerPreparedSt
atement.java:1485)
        at com.mysql.jdbc.ServerPreparedStatement.<init>(ServerPreparedStatement
.java:151)
        at com.mysql.jdbc.Connection.prepareStatement(Connection.java:1309)
        at com.mysql.jdbc.Connection.prepareStatement(Connection.java:1281)

How to repeat:
Just run 

String sql = "select * from sometable LIMIT ?,?";
PreparedStatement stmt = conn.prepareStatement(sql);

Suggested fix:
Should fix ServerPreparedStatement

This is a dupe of #4718

Since this isn't going to be fixed in the server "real-soon-now", I've patched the JDBC driver to cope:

"The community has spoken, and has not been able to wait for a server fix, 

So, by default, the driver now scans SQL you are preparing via all variants
      of Connection.prepareStatement() to determine if it is a supported 
      type of statement to prepare on the server side, and if it is not 
      supported by the server, it instead prepares it as a client-side emulated
      prepared statement (BUG#4718). You can disable this by passing 
      'emulateUnsupportedPstmts=false' in your JDBC URL.

This will ship in Connector/J 3.1.7, and 3.2.0. Nightly snapshots of 3.1.7 with
the fix applied will be available after 00:00 GMT tomorrow, February 7th for
testing from http://downloads.mysql.com/snapshots.php.

Thanks for your patience."

Setting version to 5.0 as it will be fixed there.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/25373

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/25414

First part approved and pushed. Waiting for next part

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/25610

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/25619

Fixed in 5.0 tree marked 5.0.7

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/25730

Noted in 5.0.7 changelog.