Support for pymongo 3

[markunsworth]

Support for Pymongo 3.0.

• Removed use of the fields keyword argument when calling find, as this has changed to projection in pymongo 3.0. Use positional argument instead.
• Have removed the use of safe and slave_okay keyword arguments as these are no longer used and have been deprecated since 2.4

Fix the broken tests.

• Have changed the DatabaseOperation.sqlflush method to now check if a collection is capped before trying to remove the data
• Removed tests that are no longer relevant.

Fixes #207 and #209

[markunsworth]

Fixes issues mentioned in #210

[aburgel]

I think this needs to be rebased since I merged in your safe writes PR.

[aburgel]

Can you also pull in some of the documentation updates from #208?

[markunsworth]

Ok - will merge those into this branch.

[aburgel]

@ajdavis mentioned that pymongo 2.9 will be compatible with both 2.8 and 3.0, so can we standardize on that?

If its too much work, I'm happy to cut a new version and require 3.0.

[markunsworth]

Could be an option to maintain a 0.5.x branch for supporting pymongo < 3 and use 0.6.x (master) for pymongo 3 onwards.

We can use pymongo >= 2.9, but i don't think some of the other changes (e.g. removing MongoReplicaSetClient in favour of MongoClient for connecting to replica sets) are being backported. @ajdavis might be able to clarify on that.

Pymongo 3 still supports the old crud API (find, update, remove) so I think anyone using it directly will still be able to do pretty much everything they are doing with 2.x

[ajdavis]

MongoReplicaSetClient lives on in 3.0 as a synonym for MongoClient, so you
can continue to use it.

On Tuesday, June 23, 2015, Mark Unsworth [email protected] wrote:

We can require pymongo >= 2.9, but i don't think some of the other changes
(e.g. removing MongoReplicaSetClient in favour of MongoClient for
connecting to replica sets) are being backported. @ajdavis
https://github.com/ajdavis might be able to clarify on that.

Pymongo 3 still supports the old crud API (find, update, remove) so I
think anyone using it directly will still be able to do pretty much
everything they are doing with 2.x

—
Reply to this email directly or view it on GitHub
#214 (comment)
.

[markunsworth]

There seems to be an issue since moving to use the nonrel-1.6 branch from nonrel-1.6-beta use to the use of transaction.atomic() in the flush command.

Added a workaround of setting DatabaseFeatures.can_rollback_ddl = True which works but doesn't feel right given it's not true. Ultimately that property is used to check if the atomic call should set a savepoint.

Some feedback would be useful here

[markunsworth]

ok - we now have backwards compatibility with 2.x

Have also added more configurations to the environment matrix to test against the latest 2.x and 3.x versions

[aburgel]

does django 1.7 actually work?

[markunsworth]

Not yet (am planning to look at that next). I've added it to the allowable failures for now

[aburgel]

does any of this depend on django-nonrel/django#22?

[markunsworth]

@aburgel No, django-nonrel/django#22 isn't necessary for this to work.