No performance issues known. You can check the javadoc of both methods to see how they are different.
But I would be surprised if the use of executeQuery would be the cause of your performance issues (if you have any issues).
Can someone please tell me if there are any performance issues while using executeQuery to update data using JDBC or is it better to use executeUpdate?
executeQuery() returns the resultset,so whatever data we are updating it will returns it.
but as we know when we are using executeUpdate() then it will return int which says that whether the data is updated or not.
if it return 0 that means data is not updated but if it return 1 it means data is updated.
so there is performance issue....as executeQuery have to return the whole resultset Updated.
As we have to only know whether the data is updated or not,so it will be better if we use executeUpdate while running update command.....