Improve constructorWithExplicitDialect test to verify dialect 1 numeric-as-double behavior

In SQL dialect 1, NUMERIC(18,2) columns are described as DOUBLE PRECISION
instead of scaled integers. The updated test inserts a value into a NUMERIC(18,2)
table column, then selects it using s dialect-1-prepared statement and verifies
that getDouble() retrieves the correct value, exercising the dialect-specific
type mapping.

Author: fdcastel

src/test/Statement.cpp

@@ -178,13 +178,33 @@ BOOST_AUTO_TEST_CASE(constructorWithExplicitDialect)
 	Attachment attachment{CLIENT, database, AttachmentOptions().setCreateDatabase(true)};
 	FbDropDatabase attachmentDrop{attachment};
 
+	{  // scope
+		Transaction transaction{attachment};
+		Statement createTable{attachment, transaction,
+			"create table test_dialect (amount numeric(18, 2))"};
+		createTable.execute(transaction);
+		transaction.commit();
+	}  // scope
+
+	{  // scope
+		Transaction transaction{attachment};
+		Statement insert{attachment, transaction,
+			"insert into test_dialect values (cast(1234.56 as numeric(18, 2)))"};
+		insert.execute(transaction);
+		transaction.commit();
+	}  // scope
+
 	Transaction transaction{attachment};
-	Statement stmt{
-		attachment, transaction, "select 1 from rdb$database", StatementOptions().setDialect(SQL_DIALECT_CURRENT)};
+	// In SQL dialect 1, NUMERIC(18,2) is mapped to DOUBLE PRECISION instead of
+	// a scaled integer, so getDouble() retrieves the value correctly.
+	Statement stmt{attachment, transaction, "select amount from test_dialect",
+		StatementOptions().setDialect(1u)};
 
 	BOOST_CHECK(stmt.isValid());
-	BOOST_CHECK(stmt.execute(transaction));
-	BOOST_CHECK_EQUAL(stmt.getInt32(0).value(), 1);
+	BOOST_REQUIRE(stmt.execute(transaction));
+	auto value = stmt.getDouble(0);
+	BOOST_REQUIRE(value.has_value());
+	BOOST_CHECK_CLOSE(*value, 1234.56, 0.001);
 }
 
 BOOST_AUTO_TEST_SUITE_END()