http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/MODM-124 Doctrine MongoDB ODM <p>Currently if document doesn't have "db" mapping, it is taken from defaultDb configuration and assigned to classmetadata (in ClassMetadataFactory).</p> <p>But if we have two documentManagers with different defaultDb configuration, second manager's configuration will be ignored, because "db" value is already set in classMetadata (when the 1st manager was created).</p> <p>It gets worse with metadata caching, as defaultDb setting is only taken in account when metadata is stored in cache. </p> <p>This affects a common use-case, when each customer has his own database and defaultDb is defined at runtime.</p> MODM-124

ClassMetadata shouldn't store defaultDb value

Bug Major Resolved Fixed Jonathan H. Wage Vladimir Razuvaev Fri, 18 Feb 2011 07:05:20 +0000 Fri, 4 Mar 2011 10:56:01 +0000 Fri, 4 Mar 2011 10:56:01 +0000 1.0.0BETA2 1.0.0BETA3 0 0 <p>Hi, this is fixed here <a href="https://github.com/doctrine/mongodb-odm/commit/6b91d944e68bbf94702a38351f03c74b7d6a057a" class="external-link">https://github.com/doctrine/mongodb-odm/commit/6b91d944e68bbf94702a38351f03c74b7d6a057a</a></p> <p>Thanks for reporting the issue.</p>