[RFC] Plan for MongoDB ODM v3

[GromNaN]

MongoDB ODM v2 was released in 2018 and PHP and MongoDB have come a long way since then.

I'd like to propose a plan for things that involve breaking changes and that can be achieved for a 3.0 release. The goal is to make the version 2.last version 100% compatible with 3.0, as soon as all deprecations are resolved (following the same process as Symfony of deprecating before removing).

• Drop lazy proxy libraries and use native lazy objects
  • Add support for native lazy objects in v2.x
  • Require PHP 8.4+ Require PHP 8.4 #2895
• Rename lib/Doctrine/ODM/MongoDB/ to src/ Move source files into src/ directory #2866
• Drop support for annotations. They are replaced by PHP Attributes Remove support for Doctrine Annotations #2931
• Add native types to all properties
• Add native return types
• Add native parameter types (this is backwards compatible, should be already the case)
• Make soft-final classes, hard-final
• Require ext-mongodb 2 Remove Support for ext-mongodb 1.x #2897
• Remove support for CollectionInfoIterator, CollectionInfoCommandIterator, IndexInfoIterator, IndexInfoIteratorIterator from ext-mongodb 1.x
• Remove inheritance strategies COLLECTION_PER_CLASS Deprecate COLLECTION_PER_CLASS inheritance #2742
• Make classMetadata fields private(set)
• Switching "symfony/var-dumper" in require-dev #2448
• Require composer-runtime-api: ^2.0 [3.x] Require Composer v2 #2782 (see PHPLIB-1302: Use Composer\InstalledVersions mongodb/mongo-php-library#1262)
• Use #[AsCommand] attribute to enable lazy-loading [3.x] Add types to Commands and use AsCommand attribute #2934
• Drop doctrine/cache dependency

[aturki]

A very nice addition to the v3 would be the result cache 🙂

[greg0ire]

Item 2 (renaming to src) should IMO be done in 2.x, as it is no breaking change and will make merging up easier.

[alcaeus]

A very nice addition to the v3 would be the result cache 🙂

You would typically design your schema in a way that avoids long-running queries, which is the entire point of a non-relational document database. That said, I'd be interested to hear your use case for a result cache.

[mickverm]

I noticed that this library still requires the no longer maintained and abandoned doctrine/cache dependency, is this something that will also be tackled in version 3?