Fix DBAL 3 compatibility

[williarin]

Fixes #365

doctrine:fixtures:load command no longer failing with DBAL 3.

[greg0ire]

To make this complete, I think we should allow dbal 3 the version constraint here:

data-fixtures/composer.json

Line 27 in d5ebdb4

"doctrine/dbal": "^2.5.4",

Currently, we are only testing with doctrine/dbal v2 because of it.

[greg0ire]

Maybe I approved too fast… what does this PR do?
I think it means that when upgrading to DBAL 3, tables that were previously not purged will suddenly be purged, correct?

EDIT: and then I click "Close and comment" when I mean to click comment 😅

The UPGRADE guide states the following: "Regular expression-based filters are hard to extend by combining together. Instead, you may use callback-based filers via ::getSchemaAssetsFilter() and ::getSchemaAssetsFilter(). Callbacks can use regular expressions internally.". This is not what this PR does.

[stof]

Maybe I approved too fast… what does this PR do?
I think it means that when upgrading to DBAL 3, tables that were previously not purged will suddenly be purged, correct?

Well, doctrine/data-fixtures does not configure the filtering. It uses the filtering configured in DBAL.
If you use the filtering feature of your project, you will already need to migrate to the non-deprecated feature before migrating to DBAL 3.

[greg0ire]

Oh right, I didn't notice that the new way was already handled in the lines below (because I didn't know what it looked like). It should be fine then I think.

[greg0ire]

Thanks @williarin !