Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-11369

Change in behaviour of MinKey/MaxKey

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Works as Designed
    • 2.5.2
    • None
    • Querying
    • Minor Change
    • ALL
    • Hide

      2.4.5

      > db.q.drop();
      true
      > db.q.insert({a:1});
      > db.q.find( { "a.b.c" : MinKey } )
      { "_id" : ObjectId("5269a584d627d2d0a303d37c"), "a" : 1 }

      2.5.4-pre

      > db.q.drop();
      true
      > db.q.insert({a:1});
      > db.q.find( { "a.b.c" : MinKey } )

      Show
      2.4.5 > db.q.drop(); true > db.q.insert({a:1}); > db.q.find( { "a.b.c" : MinKey } ) { "_id" : ObjectId("5269a584d627d2d0a303d37c"), "a" : 1 } 2.5.4-pre > db.q.drop(); true > db.q.insert({a:1}); > db.q.find( { "a.b.c" : MinKey } )

    Description

      Problem:
      MinKey appears to behave differently in 2.4.5 and 2.5.4-pre

      Attachments

        Issue Links

          Activity

            People

              eliot Eliot Horowitz (Inactive)
              alvin Alvin Richards (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: