Claudio Zizza

Thanks for taking a look at this. I currently see that another rewrite would be needed to get the expected rowspan for this use case :disappointed:

"vimeo/psalm": "^5.9.0" => vimeo/psalm (5.24.0) The last build of 2.7.x must have been on a different psalm version

I assume this part of the docs is meant: https://www.doctrine-project.org/projects/doctrine-mongodb-odm/en/latest/reference/custom-mapping-types.html Do we need to target a specific branch for the extended information?

Why do you need a certain case for the unique constraint? Wouldn't this suggest to use a case insensitive column collation?

Hi @beregovoy it does make sense to have some expectations about the order of executed, but changing this in version 3.7 would be a bc break. I'd expect that this...

Thank you for the PR, @ottaviano. Did you run into a specific problem that resulted into this change?

Good catch. D you like to create a PR to remove the option from the docs and adapt the output of `status`?

You can push your dev-branch to Github to view your current changes or use a rst-viewer (e.g. the one in PHPStorm).

If the helper class is kept in 4.0, it can only be removed in a 5.0 release, right? It doesn't seem to be widely in use now.

Can you please provide a mapping example that results in that behaviour?