Nicolas PHILIPPE

Hi, thanks for this, sorry for the late reply on your issue ~I think you need to update method `dropAndResetDatabase()` as well.~ I also think you need to pass `--complete`...

> Where in that method? It doesn't create the schema. yeah sorry, I misread, it is a `doctrine:database:create`, I'll correct my comment

I'm just a bit worried of implications of this change: won't this be a big BC for people who have tables not managed by the ORM in the same db?...

Hi @haase-fabian > Everytime the test suite is run, when there is a TestCase using the ResetDatabase trait, the database is reset. This statement is not true when using dama...

Hey @haase-fabian this is just an idea, but do you think we could somehow leverage the proposal [here](https://github.com/zenstruck/foundry/issues/540)? and manage what you want to achieve is userland based on an...

Hi @lsv I think you can leverage [global state](https://symfony.com/bundles/ZenstruckFoundryBundle/current/index.html#global-state) here. I have a similar problem: I need some sql views to be created in order to be used in the...

Hi @lhapaipai indeed, you're right! Maybe you could enable `migrate` mode for the database resetter? You can look at this issue: https://github.com/zenstruck/foundry/issues/477 This comes with a performance cost, which makes...

If you use dama, the performance cost is really limited, since the migrations are only ran once. Maybe this whole problem could be solved by introducing some kind of events...

I can see the command `doctrine:schema:drop` have the option `--full-database`, shouldn't we use it if it does not drop all schemas?

> Got it, thanks for the explanation! @nikophil, could this in anyway be related to https://github.com/zenstruck/foundry/pull/458/https://github.com/zenstruck/foundry/issues/455? I think it's not related: #458 only kills active connections to the db in...