Uploaded image for project: 'Doctrine MongoDB ODM'
  1. Doctrine MongoDB ODM
  2. MODM-124

ClassMetadata shouldn't store defaultDb value

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0BETA2
    • Fix Version/s: 1.0.0BETA3
    • Component/s: None
    • Labels:
      None

      Description

      Currently if document doesn't have "db" mapping, it is taken from defaultDb configuration and assigned to classmetadata (in ClassMetadataFactory).

      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).

      It gets worse with metadata caching, as defaultDb setting is only taken in account when metadata is stored in cache.

      This affects a common use-case, when each customer has his own database and defaultDb is defined at runtime.

        Activity

        Hide
        jwage Jonathan H. Wage added a comment -
        Show
        jwage Jonathan H. Wage added a comment - Hi, this is fixed here https://github.com/doctrine/mongodb-odm/commit/6b91d944e68bbf94702a38351f03c74b7d6a057a Thanks for reporting the issue.

          People

          • Assignee:
            jwage Jonathan H. Wage
            Reporter:
            vladar Vladimir Razuvaev
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: