* Import doctrine/mongodb-odm-bundle recipes from contrib
* Add alias 'mongodb-odm' for 'doctrine/mongodb-odm-bundle'
* No need to resolve MONGODB_URL env var
This recipe avoids getting deprecations from the ORM by turning on new
settings.
For the identity generation precedence, using `identity` is the best
choice for new projects (especially when using DBAL 4.x from the start).
By default, root user is used to connect to the database.
If the database does not have a "root" role, the following error is logged everytime the health check happens: 'FATAL: role "root" does not exist', which spams the log.
* Add mariadb example to DATABASE_URL
* Apply change requests
* Use same casing as in the doctrine/dbal mariadb docs
See https://github.com/doctrine/dbal/pull/5971
* Update doctrine/doctrine-bundle/2.8/manifest.json
Co-authored-by: Alexander M. Turek <me@derrabus.de>
* Use only major version for postgresql serverVersion
---------
Co-authored-by: Alexander M. Turek <me@derrabus.de>
When auto_generate_proxy_classes: false is set, the proxies need to be pre-generated with the cache warmer. So in this case, the files are much better suited in the build dir. The build dir is the same as the cache dir by default. But for people trying to use the build dir properly, this makes much more sense. See https://github.com/symfony/symfony/issues/40827#issuecomment-820653578
Because of backward-compatibility reasons, not specifying the charset
will result in "utf8" being used, which is a deprecated charset.
Also, when the charset for creating tables is not specified, the one
specified in the DSN is reused if specified.
In the future, DBAL is going to drop default values, which means we will
have to specify a charset anyway.
PostgreSQL is configured in docker-compose.yaml file in the same manifest but with another configuration.
The purpose of this commit is to make it ready by default to reduce what the user is supposed to change at install time.