Skip to content
Commits on May 3, 2011
  1. @aheckmann

    fix global var leak

    aheckmann committed May 3, 2011
  2. @bnoguchi

    Fixed GH-307.

    bnoguchi committed May 3, 2011
  3. @bnoguchi
  4. @bnoguchi
Commits on Apr 29, 2011
  1. @aheckmann

    remove unused modules

    aheckmann committed Apr 29, 2011
  2. @aheckmann

    update node-mongodb-native

    aheckmann committed Apr 29, 2011
  3. @aheckmann
  4. @aheckmann
Commits on Apr 28, 2011
  1. @fabrizim @aheckmann
  2. @aheckmann

    add failing test for GH-390

    aheckmann committed Apr 28, 2011
  3. @aheckmann
  4. @aheckmann
  5. @aheckmann

    fixed; finding by Date now works as expected

    closes #336
    aheckmann committed Apr 28, 2011
  6. @aheckmann
Commits on Apr 27, 2011
  1. @aheckmann

    release 1.3.3

    aheckmann committed Apr 27, 2011
  2. @aheckmann

    minor refactoring

    aheckmann committed Apr 27, 2011
  3. @aheckmann
  4. @aheckmann
  5. @aheckmann

    release 1.3.2

    aheckmann committed Apr 27, 2011
  6. @aheckmann
  7. @aheckmann

    release 1.3.1

    aheckmann committed Apr 27, 2011
  8. @aheckmann

    no need to slice the arguments

    aheckmann committed Apr 27, 2011
  9. @aheckmann

    add Query#hint support

    aheckmann committed Apr 27, 2011
  10. @aheckmann
  11. @bnoguchi

    Fixed GH-334

    bnoguchi committed Apr 26, 2011
  12. @bnoguchi

    Added failing test for GH-334

    bnoguchi committed Apr 26, 2011
Commits on Apr 26, 2011
  1. @aheckmann
  2. @aheckmann

    add test for utils.options

    aheckmann committed Apr 26, 2011
  3. @aheckmann
  4. @aheckmann
Commits on Apr 23, 2011
  1. @aheckmann
  2. @aheckmann

    added; db.setProfiling()

    use to enable, disable, modify your db profiling level
    
    Example:
      db.setProfiling('slow', 50, callback); // turns profiling on for queries that take longer than 50 ms
      db.setProfiling('off', callback);      // turns off profiling
      db.setProfiling('all', callback);      // turns profiling on for all queries
    
    Once enabled use the default `system.profile` model to query the
    profile data.
      db.model('system.profile').find({...}, callback); // etc
    aheckmann committed Apr 23, 2011
  3. @aheckmann

    system.profile is now a default model/schema

    You can just call db.model('system.profile') to start
    querying the profiling data when mongodb profiling
    is enabled. No need to set up custom schemas for this.
    aheckmann committed Apr 23, 2011
  4. @aheckmann
  5. @aheckmann
Something went wrong with that request. Please try again.