[#2464] Skip query parameter processing

We used it to replace parameter markers for queries because
Vert.x doesn't support the JDBC syntax and our own
implementation of `ParameterMarkerStrategy` was not enough
in the past.

Now all tests pass even without the processing the query.

Author: DavideD

hibernate-reactive-core/src/main/java/org/hibernate/reactive/query/sql/internal/ReactiveNativeNonSelectQueryPlan.java

@@ -5,7 +5,6 @@
  */
 package org.hibernate.reactive.query.sql.internal;
 
-
 import java.util.ArrayList;
 import java.util.Collections;
 import java.util.List;
@@ -20,7 +19,6 @@
 import org.hibernate.query.sql.spi.ParameterOccurrence;
 import org.hibernate.query.sqm.internal.SqmJdbcExecutionContextAdapter;
 import org.hibernate.reactive.engine.spi.ReactiveSharedSessionContractImplementor;
-import org.hibernate.reactive.pool.impl.Parameters;
 import org.hibernate.reactive.query.sql.spi.ReactiveNonSelectQueryPlan;
 import org.hibernate.reactive.sql.exec.internal.StandardReactiveJdbcMutationExecutor;
 import org.hibernate.sql.exec.internal.JdbcParameterBindingsImpl;
@@ -71,10 +69,8 @@ public CompletionStage<Integer> executeReactiveUpdate(DomainQueryExecutionContex
 							}
 
 							final SQLQueryParser parser = new SQLQueryParser( sql, null, session.getFactory() );
-
-							Parameters parameters = Parameters.instance( session.getDialect() );
 							final JdbcOperationQueryMutation jdbcMutation = new JdbcOperationQueryMutationNative(
-									parameters.process( parser.process() ),
+									parser.process(),
 									jdbcParameterBinders,
 									affectedTableNames
 							);

hibernate-reactive-core/src/main/java/org/hibernate/reactive/sql/results/internal/ReactiveDeferredResultSetAccess.java

@@ -14,7 +14,6 @@
 import org.hibernate.HibernateException;
 import org.hibernate.JDBCException;
 import org.hibernate.LockOptions;
-import org.hibernate.dialect.Dialect;
 import org.hibernate.engine.jdbc.spi.JdbcServices;
 import org.hibernate.engine.jdbc.spi.SqlStatementLogger;
 import org.hibernate.engine.spi.SessionEventListenerManager;
@@ -24,7 +23,6 @@
 import org.hibernate.reactive.logging.impl.Log;
 import org.hibernate.reactive.logging.impl.LoggerFactory;
 import org.hibernate.reactive.pool.ReactiveConnection;
-import org.hibernate.reactive.pool.impl.Parameters;
 import org.hibernate.reactive.session.ReactiveConnectionSupplier;
 import org.hibernate.reactive.session.ReactiveSession;
 import org.hibernate.reactive.util.impl.CompletionStages;
@@ -172,11 +170,6 @@ private CompletionStage<ResultSet> executeQuery() {
 		return completedFuture( logicalConnection )
 				.thenCompose( lg -> {
 					LOG.tracef( "Executing query to retrieve ResultSet : %s", getFinalSql() );
-
-					Dialect dialect = executionContext.getSession().getJdbcServices().getDialect();
-					// This must happen at the very last minute in order to process parameters
-					// added in org.hibernate.dialect.pagination.OffsetFetchLimitHandler.processSql
-					final String sql = Parameters.instance( dialect ).process( getFinalSql() );
 					Object[] parameters = PreparedStatementAdaptor.bind( super::bindParameters );
 
 					final SessionEventListenerManager eventListenerManager = executionContext
@@ -186,7 +179,7 @@ private CompletionStage<ResultSet> executeQuery() {
 
 					eventListenerManager.jdbcExecuteStatementStart();
 					return connection()
-							.selectJdbc( sql, parameters )
+							.selectJdbc( getFinalSql(), parameters )
 							.thenCompose( this::validateResultSet )
 							.whenComplete( (resultSet, throwable) -> {
 								// FIXME: I don't know if this event makes sense for Vert.x