Support passing additional options to getLastError about txmongo HOT 2 CLOSED

getLastError is not reliable atm, since there is no way to lock a connection between e.g. an update and getLastError - thus while waiting for one getLastError response, another error could occour on that connection or some operation could succeed, resulting in a lost error feedback. Same holds true when using 'safe'.

We should fix that first before adding further features. It could be done somewhat similar to how the Java driver[1] ensures threadsafety. The pool should employ a DeferredQueue to (re)cycle busy connections. Will start doing that if i can find that thing called time again ..

[1]http://www.mongodb.org/display/DOCS/Java+Driver+Concurrency

from txmongo.

Since 15.1.0 release TxMongo supports Write-Concern options:

• For old-style query methods write-concern options can be passed as named args: coll.insert(..., w=1, j=True). Specified write-concern options will be passed to getLastError.
• For new-style query methods (*_one, *_many) write-concern options can be set using Collection.with_options method: coll.with_options(write_concern=WriteConcern(w=2, j=True)).insert_one(...). Write-concern options will be passed to corresponding MongoDB query command.

So this issue is't relevant anymore

from txmongo.