Don't reset cursors during transaction begin or commit (only on rollback).
src/docs/tune-durability.dox:67: warning: multiple use of section label 'durability_group_commit'
Merge with develop.
Reset a cursor used for updates, now that commit no longer does that for us.
Opening a cursor on a non-existent table (which MongoDB does to test for existence) should not force transactions to rollback.
whitespace
Merge branch 'develop' into no-txn-reset-cursors
update auto-generated file
Be a little more emphatic, so applications make this change.
whitespace
Don't use the phrase "open cursors", I'm not clear on what it might
mean to reset a "closed" cursor.
Fix begin_transaction's comment, there may be cursors positioned.
More documentation changes: explicit calls to begin_transaction and
commit_transaction no longer reset cursors, remove wording talking
about copying a key and re-positioning the cursor after a transaction
boundary.

Fix up the sample code to match the new semantics.
nit
s/rolled-back/rolled back/g
Merge branch 'develop' into no-txn-reset-cursors

Conflicts:
	src/include/wiredtiger.in
Handle ENOENT returns from open_cursor forcing transaction rollback in the open_cursor call, rather than further complicating the API_END macro.
Fix some "implicit conversion loses integer precision" warnings.
Some more integer conversion warnings.
Merge pull request #1181 from wiredtiger/no-txn-reset-cursors

Don't reset cursors during transaction begin or commit