Fix extra SQL support in Doctrine migrations

Author: fabpot

SchemaListener/MessengerTransportDoctrineSchemaSubscriber.php

@@ -64,8 +64,7 @@ public function onSchemaCreateTable(SchemaCreateTableEventArgs $event): void
                 continue;
             }
 
-            $extraSql = $transport->getExtraSetupSqlForTable($table);
-            if (null === $extraSql) {
+            if (!$extraSql = $transport->getExtraSetupSqlForTable($table)) {
                 continue;
             }
 
@@ -79,7 +78,9 @@ public function onSchemaCreateTable(SchemaCreateTableEventArgs $event): void
              * the only way to inject some extra SQL.
              */
             $event->addSql($createTableSql);
-            $event->addSql($extraSql);
+            foreach ($extraSql as $sql) {
+                $event->addSql($sql);
+            }
             $event->preventDefault();
 
             return;

Tests/SchemaListener/MessengerTransportDoctrineSchemaSubscriberTest.php

@@ -61,7 +61,7 @@ public function testOnSchemaCreateTable()
         $doctrineTransport->expects($this->once())
             ->method('getExtraSetupSqlForTable')
             ->with($table)
-            ->willReturn('ALTER TABLE pizza ADD COLUMN extra_cheese boolean');
+            ->willReturn(['ALTER TABLE pizza ADD COLUMN extra_cheese boolean']);
 
         // we use the platform to generate the full create table sql
         $platform->expects($this->once())
@@ -87,7 +87,7 @@ public function testOnSchemaCreateTableNoExtraSql()
         $doctrineTransport = $this->createMock(DoctrineTransport::class);
         $doctrineTransport->expects($this->once())
             ->method('getExtraSetupSqlForTable')
-            ->willReturn(null);
+            ->willReturn([]);
 
         $platform->expects($this->never())
             ->method('getCreateTableSQL');