Here's a clearer explanation of query execution methods and proposed changes:
Statement/PreparedStatement offers three execution methods:

• execute(): Handles any SQL statement type, returns boolean indicating if result is a ResultSet
• executeUpdate(): For DML (INSERT/UPDATE/DELETE) and DDL statements that don't return data. Returns update count.
• executeQuery(): For SELECT and other queries returning data. Currently requires ResultSet return, throwing exception if none exists.

Proposed Change:
When executeQuery() executes a command producing no ResultSet, return empty ResultSet instead of throwing exception. This improves backward compatibility and user experience. An option will permit strict JDBC compliance but disabled by default.

Implementation Note:
Unlike MySQL Connector/J, we won't parse queries to pre-validate ResultSet production, as this creates unnecessary performance overhead