From c30dd8d6b0e94cf4b43e513a4ebd713f91703334 Mon Sep 17 00:00:00 2001 From: David Cook Date: Tue, 20 Jun 2023 06:20:00 +0000 Subject: [PATCH] Bug 34064: Remove no_batch_alters option This change removes the no_batch_alters option. When working with real world databases, you really want to use batch alters to group together changes. Otherwise, the output becomes too overwhelming/unwieldy. On real world databases, I'm noticing big discrepancies, although I think most of the time this is a difference in the collation at the column level. Signed-off-by: Owen Leonard Signed-off-by: Martin Renvoize Signed-off-by: Tomas Cohen Arazi --- misc/maintenance/audit_database.pl | 1 - 1 file changed, 1 deletion(-) diff --git a/misc/maintenance/audit_database.pl b/misc/maintenance/audit_database.pl index d84d9af93f..d64f9bbc43 100755 --- a/misc/maintenance/audit_database.pl +++ b/misc/maintenance/audit_database.pl @@ -25,7 +25,6 @@ if ($sql_schema && $db_schema){ output_db => 'MySQL', source_schema => $db_schema, target_schema => $sql_schema, - no_batch_alters => 1, })->compute_differences->produce_diff_sql; print $diff; -- 2.39.5