[#1546] Replace SqlServerDialect version

When using a dialect for SqlServer with version higher or equal to 11,
Vert.x cannot run the query for retrieving the information about the
sequences.

While we wait for the bug to be fixed, we rely on the dialect version
10.

Author: DavideD

hibernate-reactive-core/src/main/java/org/hibernate/reactive/logging/impl/Log.java

@@ -14,6 +14,7 @@
 import org.hibernate.HibernateException;
 import org.hibernate.LazyInitializationException;
 import org.hibernate.cache.CacheException;
+import org.hibernate.dialect.Dialect;
 import org.hibernate.id.IdentifierGenerationException;
 
 import org.jboss.logging.BasicLogger;
@@ -284,6 +285,10 @@ public interface Log extends BasicLogger {
 	@Message(id = 353, value = "Could not release a cache lock : %s" )
 	void unableToReleaseCacheLock(CacheException ce);
 
+	@LogMessage(level = WARN)
+	@Message(id = 400, value= "Changing dialect '%1$s' to '%2$s'")
+	void replacingDialect(Dialect from, Dialect to);
+
 	// Same method that exists in CoreMessageLogger
 	@LogMessage(level = WARN)
 	@Message(id = 447, value= "Explicit use of UPGRADE_SKIPLOCKED in lock() calls is not recommended; use normal UPGRADE locking instead")

hibernate-reactive-core/src/main/java/org/hibernate/reactive/provider/service/NoJdbcEnvironmentInitiator.java

@@ -9,11 +9,15 @@
 import java.util.concurrent.CompletionStage;
 
 import org.hibernate.boot.registry.StandardServiceInitiator;
+import org.hibernate.dialect.DatabaseVersion;
 import org.hibernate.dialect.Dialect;
+import org.hibernate.dialect.SQLServerDialect;
 import org.hibernate.engine.jdbc.dialect.spi.DialectFactory;
 import org.hibernate.engine.jdbc.dialect.spi.DialectResolutionInfo;
 import org.hibernate.engine.jdbc.env.spi.JdbcEnvironment;
 import org.hibernate.reactive.engine.jdbc.env.internal.ReactiveJdbcEnvironment;
+import org.hibernate.reactive.logging.impl.Log;
+import org.hibernate.reactive.logging.impl.LogCategory;
 import org.hibernate.reactive.pool.ReactiveConnection;
 import org.hibernate.reactive.pool.ReactiveConnectionPool;
 import org.hibernate.reactive.provider.Settings;
@@ -23,6 +27,7 @@
 
 import io.vertx.sqlclient.spi.DatabaseMetadata;
 
+import static org.hibernate.reactive.logging.impl.LoggerFactory.make;
 import static org.hibernate.reactive.util.impl.CompletionStages.failedFuture;
 
 /**
@@ -32,6 +37,11 @@
  */
 public class NoJdbcEnvironmentInitiator  implements StandardServiceInitiator<JdbcEnvironment> {
 
+	/**
+	 * I'm using the same logger category used in {@link org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl}
+	 */
+	private static final Log LOG = make( Log.class, new LogCategory( "SQL dialect" ) );
+
 	public static final NoJdbcEnvironmentInitiator INSTANCE = new NoJdbcEnvironmentInitiator();
 
 	@Override
@@ -63,7 +73,25 @@ public DialectBuilder(Map<String, Object> configurationValues, ServiceRegistry r
 
 		public Dialect build() {
 			DialectFactory dialectFactory = registry.getService( DialectFactory.class );
-			return dialectFactory.buildDialect( configurationValues, this::dialectResolutionInfo );
+			Dialect dialect = dialectFactory.buildDialect( configurationValues, this::dialectResolutionInfo );
+			dialect = checkDialect( dialect );
+			return dialect;
+		}
+
+		/**
+		 * Workaround for <a href="https://github.com/eclipse-vertx/vertx-sql-client/issues/1312">vertx-sql-client#1312</a>
+		 * <p>
+		 * For extracting the information about sequences, the Sql Server dialect 11+ uses the following query:
+		 * <pre>{@code select * from INFORMATION_SCHEMA.SEQUENCES}</pre>
+		 * But, the Vert.x MSSQL client throws an exception when running it.
+		 */
+		private static Dialect checkDialect(Dialect dialect) {
+			if ( dialect instanceof SQLServerDialect && dialect.getVersion().isSameOrAfter( 11 ) ) {
+				SQLServerDialect sqlServerDialect = new SQLServerDialect( DatabaseVersion.make( 10 ) );
+				LOG.replacingDialect( dialect, sqlServerDialect );
+				return sqlServerDialect;
+			}
+			return dialect;
 		}
 
 		private DialectResolutionInfo dialectResolutionInfo() {