- Various fixes to allow test_async01.py to work for string key/value.
- Hand rolled AsyncCallback class to mirror C's WT_ASYNC_CALLBACK.
- Keep the async callback in the PY_CALLBACK struct hidden in cursor's
lang_private.
- Some cleanups in writeToPythonStream(), including fixing
potential race condition.
Java for async:
- Modified Java SWIG interfaces for async enough to allow it compile.
- Standardized class spelling to 'AsyncOp'.
- Removed a few non-applicable methods from AsyncOp.
will not crash the VM on use. ref #485
Uses the event callback for close to give notification on close
of a handle. For explicit calls to close(), we set the SWIG 'this'
attribute on the containing object to None.
On uses of a handle as an input argument, we check to see if it is
None, or if its 'this' attribute is None, and issue the
appropriate exception.
Includes a set of test cases that parallel Java test cases for the same.
Cleaned up test suite infrastructure a bit using this.
Any verbose messages from the infrastructure itself do not get captured.
refs #649
test_reconfig.py needed special treatment. Verbose output from
threads is not necessarily flushed until the connection is closed;
we reopen the connection to force the flush so that the test should
pass on all platforms.
refs #698
a default of wiredtiger_extension_unload.
Rename "entry" load extension entry point to be "load", rename the default
from wiredtiger_extension_init to wiredtiger_extension_load, to match.
a new function wiredtiger_extension_api(WT_EXTENSION_API **pp).
Write some WT_EXTENSION_API documentation.
Remove WT_SESSION::msg_printf, add a new msg_printf extension function
instead, convert test/format to use it.
Quit using __UNUSED in the extension code, use explicit (void) casting,
it's cleaner.
Merge statistics from file and LSM sources into a "data source" statistic structure. Rename and regroup some shared stastistics. Make statistics constant names upper case. Add a helper to the Python API to lookup in a cursor in a simple expression.
closes#232
This avoids making calls into Python's C API from our methods. The problem with that is that in SWIG "thread" mode, we are not holding the Python interpreter lock, and some Python functions (including allocation functions) expect to be single-threaded.
While in the area, prefer generic SWIG macros to Python-specific ones and avoid int returns that are used purely for error checking.
closes#374
equality result in a separate argument: close#274.
Add connection.is_new to the list of methods in the SWIG file that don't
require error handling, add a connection.is_new smoke test to the test
suite.
Add a connection.get_home smoke test to the test suite.