#4603 Rework Ming's DataStore to simplify connections

v1.0.0
closed
None
General
2015-08-20
2012-07-24
No

The code in ming.datastore has multiple problems

  • it replicates existing pymongo functionality
  • it doesn't support ReplicaSetConnections (which is the only way you can do read_preference)
  • its support for master/slave replication is rather first class for a deprecated deployment scenario

Rip out the existing datastore/engine and replace it with something that returns native pymongo objects (mim.Connection, Connection, ReplicaSetConnection, or MasterSlaveConnection rather than Engine and Database rather than DataStore)

Discussion

  • Rick Copeland - 2012-07-25
    • status: in-progress --> code-review
    • qa: Dave Brondsema
     
  • Rick Copeland - 2012-07-25

    Code is on rc/4603 and requires updating Ming

    QA is running the tests and poking around with sharp sticks to ensure no regressions. Nothing visible should change.

    NOTE however that this requires .ini file changes, particularly unifying the 'master' and 'database' arguments for ming config. This will require communication with SiteOps.

     
  • Dave Brondsema

    Dave Brondsema - 2012-07-27
    • status: code-review --> closed
    • size: 4 --> 0
    • milestone: forge-backlog --> forge-aug-10
     

Log in to post a comment.