Add Parameters to the Output of Dry Run Migrations

[chrisguitarguy]

Closes #186

Right now this looks like...

    -> INSERT INTO whatever VALUES (?, ?) with parameters (one, two)

with numeric indices in the param array. If there are string indices, those names are included in the output (under the assumption that they match placeholders in the SQL).

    -> INSERT INTO whatever VALUES (:one, :two) with parameters (:one => one, :two => two)

The DBAL type classes are used to convert the values to something suitable for output (specifically Type::convertToDatabaseValue.

SQL statements without any params look the same as they do currently.

This is probably a good enough first pass at this, but it's not going to protect users from doing something wonky like...

$this->addSql('INSERT INTO whatever VALUES (?)', [new \stdClass]);

and causing it the dryrun fail (granted the migration itself would fail anyway).

In other words: there's not a lot of validation. But that's not necessarily a bad thing. Types aren't validated to make sure they exist before fetching them with Type::getType(...), but that's something thay may help a user catch bugs.

[mikeSimonson]

@chrisguitarguy I like this. Can you add a test with a datetime being passed ?

[chrisguitarguy]

Added, @mikeSimonson. Also added a test for an array type. The test is setup to be able to easily add more types if necessary.

[mikeSimonson]

@chrisguitarguy Thanks