- 18 Jun, 2016 1 commit
-
-
Jim Fulton authored
Move load to imvcc storage
-
- 17 Jun, 2016 9 commits
-
-
Jim Fulton authored
Which led to me to call site that needed it to be removed.
-
Jim Fulton authored
And finally get rid of the version argument. Also drop the version argument from IStorageWrapper.invalidate.
-
Jim Fulton authored
Stop calling load
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
Load calls load before
-
Jim Fulton authored
Conflicts: src/ZODB/utils.py
-
Jim Fulton authored
-
- 16 Jun, 2016 5 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
Because the error semantics of load and loadBefore differ enough that changing calls isn't trivial. Plus the helper serves as a handy transitional load implementation.
-
Jim Fulton authored
Simplify MVCC by determining transaction start time using lastTransac…
-
Jim Fulton authored
Obviously the tests don't call this. This is probably because they use DB.storage (rather than DB._mvcc_storage).
-
Jim Fulton authored
-
- 15 Jun, 2016 14 commits
-
-
Jim Fulton authored
Conflicts: setup.py src/ZODB/tests/synchronizers.txt
-
Jim Fulton authored
Abstract ZODB's MVCC implementation into a storage adapter.
-
Jim Fulton authored
- Lower-weight instances when not using RelStorage - Still works with new RelStorage instances. - Doesn't make me include loadBefore in MVCCAdapterInstance objects. :)
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
Hopefully, this will make linters happier.
-
Jim Fulton authored
I'd started to edit it to remove implementation details and got distracted, leaving it half edited.
-
Jim Fulton authored
-
Jim Fulton authored
This allows us to not worry about method overriding and avoids creating wrapper methods (some of which were broken). My guess is that performance is a wash. We take a tiny hit on the first access, because ``__getattr__``, but we don't have to copy methods we never use.
-
Jim Fulton authored
-
Jim Fulton authored
It wasn't really needed or used and caused a stupid ZEO test failure. I do think the storage API needs to be thought about and refined at some point, but now, it's not a priority.
-
Jim Fulton authored
I'd lazily assumed that undo and tpc_vote has the same sorts of returns, but they don't. When tpc_vote isn't None (ZEO), the retrun is a list of oid and serial pairs.
-
Jim Fulton authored
To prevent modifying the set of instances while iterating over them.
-
- 14 Jun, 2016 1 commit
-
-
Jim Fulton authored
That's applied to storages other than RelStorage. See: https://groups.google.com/forum/#!topic/zodb/QJYmvF0eUUM
-
- 13 Jun, 2016 2 commits
-
-
Jim Fulton authored
Fix winbot failures Thanks
-
Jim Fulton authored
-
- 11 Jun, 2016 6 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
This fixes the following random failure: Failure in test checkBaseHistory (ZODB.tests.testDemoStorage.DemoStorageTests) Traceback (most recent call last): File "unittest\case.py", line 384, in _executeTestPart function() File "ZODB\tests\testDemoStorage.py", line 96, in checkBaseHistory self._checkHistory(base_only()) File "ZODB\tests\HistoryStorage.py", line 46, in _checkHistory self.assertLess(a, b) File "unittest\case.py", line 1026, in assertLess self.fail(self._formatMessage(msg, standardMsg)) File "unittest\case.py", line 508, in fail raise self.failureException(msg) AssertionError: 1465433823.260304 not less than 1465433823.260304
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
And in special case where a connectin is opened while a transaction is active (Zope2).
-
- 10 Jun, 2016 2 commits
-
-
Jim Fulton authored
It's too hard to remember to update the meta data (we've been in beta for a long long time).
-
Jim Fulton authored
-