Nicolas PHILIPPE

I think this is still not possible: ``` Problem 1 - doctrine/mongodb-odm-bundle[5.0.0-RC1, ..., 5.1.x-dev] require doctrine/mongodb-odm ^2.6 -> satisfiable by doctrine/mongodb-odm[2.6.0, ..., 2.9.x-dev]. - doctrine/mongodb-odm-bundle[4.6.0, ..., 4.7.x-dev] require doctrine/mongodb-odm ^2.3...

waiting for https://github.com/laminas/laminas-code/pull/201

Hi @MatTheCat this is totally doable, but only in v2 (you mentioned you were using v2 in a previous issue)

I'm wondering what's the best approach. I've never used this `--configuration` option. Is it the same file than the one in `config/packages/doctrine_migrations.php` ([this one?](https://symfony.com/bundles/DoctrineMigrationsBundle/current/index.html#configuration)). If so, shouldn't be already loaded...

ho OK, I missed the plural :) Maybe we could update Foundry's config this way? WDYT? ```diff orm: reset: connections - default entity_managers: - default mode: schema # or "migrate"...

to be totally honest, I was thinking we were passing the ems and/or the connections to `doctrine:migrations:migrate`, but we actually don't. I'm not using this reset mode at all, and...

for the schema, we're using all `entity_managers` given, which makes sense: from the EM you can guess the related connection

BTW, I'm on holidays this evening, and I cannot do it today. Feel free to provide a PR, but I won't be able to review before 2 weeks

@divine actually I'm wondering if `RangeFilter` is the right filter to modify: it would feel weird to configure a range filter on a string property, for instance :thinking:

yeah this could be a good idea... I still need to work on this one and think of a good real life example to convince @kbond :laughing: I'm not really...