Copy maxFeatureCompatibilityVersion when copying the ExpressionContext

XMLWordPrintableJSON

    • Query
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      While implementing SERVER-41257 we noticed that this wasn't happening. The perceivable effect (not tested) is that you can sneak a 4.0-only expression into a view definition even while the feature compatibility version is 3.6.

            Assignee:
            Backlog - Query Team (Inactive)
            Reporter:
            Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: