- Sep 03, 2020
- Aug 31, 2020
- Aug 07, 2020
-
-
iFA authored
-
- Jul 19, 2020
- May 18, 2020
- Apr 07, 2020
- Mar 12, 2020
- Apr 22, 2019
- Apr 19, 2019
-
-
Ming-Hsuan-Tu authored
-
Ming-Hsuan-Tu authored
-
- Apr 18, 2019
-
-
Ming-Hsuan-Tu authored
-
- Apr 06, 2019
-
-
Ming-Hsuan-Tu authored
-
- Feb 02, 2019
-
-
Ming-Hsuan-Tu authored
Allow `rocksdb.DB` instances to be manually closed (second revision PR)
-
twmht authored
-
- Feb 01, 2019
-
-
Alexander Böhn authored
While `delete rocks_ptr` is a deterministic operation in C++, the Python analogue `del rocks_handle` is not – disposal and finalization of the Rocks database are entirely dependent on the Python garbage collector (q.v. the `python-rocksdb` tests themselves, which call `gc.collect()` after `del rocks_handle` to attempt to force the destructor to run). This change exposes a method to trigger the destruction of the underlying Rocks database pointer (deterministic!) through the Python Rocks handle; existing code will not need to be changed, as the Python object destructor (non-deterministic!) will now call this method. This is the second revision of this PR – it resolves the first revision, #39.
-
twmht authored
-