Grégoire Paris

If it works as you expect in the sandbox, then it must be a bug. Please use `git bisect` to find the commit that introduced it. The author will be...

Oh right... any idea how to fix this?

Sorry I meant "fixing sonata-project/SonataAdminBundle@9655c1e#commitcomment-22646949"

I'm not OP, but I think the only method from which it should be removed is `with` https://github.com/sebastianbergmann/phpunit/blob/004ea3b3edc88ac9263ddbd50eb818cff51c591e/src/Framework/MockObject/Runtime/Interface/InvocationStubber.php#L46 For `will*`, there are variadic arguments, but it does not make sense...

From the documentation you linked: > SchemaTool will not detect changes on the column correctly anymore if you use columnDefinition. If the ORM's schema tool cannot detect the changes, why...

I think it has been a lost cause in the past, but now that we have platform-aware comparison, it _might_ be thinkable. Also, I don't think the limitation will have...

Hi! After reading [this thread](https://github.com/doctrine/DoctrineBundle/issues/1654), I think the result cache is unlikely to get cleared between deploys. Because of that, there will be a performance hit. What else will there...

I see what you mean. Here is another idea: what if, upon detecting an old version of the cache, we threw a dedicated exception instead of letting the users get...

> we can split ArrayResult into the actual object to be cached Sorry, I don't understand what you mean by that, can you elaborate? Regarding the warning, I think that...

Thanks for the explanation, I think moving towards more object is a good idea. Using objects will result in a slightly bigger cache because of the way `serialize()` works, but...