Fix for Jakarta data issue #2183

[ajaypaul-ibm]

This PR contains the workaround for #2183.(Jakarta Data issue )
This will work if update query is structured like :

• UPDATE Coordinate SET x = :newX, y = y / :yDivisor WHERE id = :id (Here we have 2 parameters x and y in SET clause and also we have a "id" in the WHERE clause)

• UPDATE Coordinate SET x = :newX, y = y / :yDivisor (This solution will work even if WHERE clause is not there)

• UPDATE Coordinate SET x = :newX, (This solution will work for simple update queries )

Please note : This is not a general solution for all types of update queries. This will work only for the type of Jakarta update queries which are mentioned above.

[OndroMih]

I believe that #2183 is already fixed in master branch by #2218. Please try it.