- 12 May, 2000 1 commit
-
-
Jim Fulton authored
-
- 09 May, 2000 6 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
when tpc_begin failed.
-
- 05 May, 2000 2 commits
-
-
Jim Fulton authored
implementation a little more orthodox and, more importantly, allows ZEO perform stores asynchronously (and then synchronize on the vote).
-
Jim Fulton authored
-
- 21 Apr, 2000 2 commits
-
-
Jim Fulton authored
-
Tres Seaver authored
-
- 20 Apr, 2000 2 commits
-
-
Chris McDonough authored
-
Chris McDonough authored
Made unpickler show the data from a pickled instance when it can't load the object from the ZODB for whatever reason. Helps when trying to debug why your object won't load.
-
- 14 Apr, 2000 1 commit
-
-
Jim Fulton authored
This reduced the amount of code and should make the next step, adding failure handling, much easier. Also changed invalidation protocol to be atomic (or close enough).
-
- 13 Apr, 2000 1 commit
-
-
Tres Seaver authored
-
- 12 Apr, 2000 1 commit
-
-
Jim Fulton authored
skip oid DECREFing logic.
-
- 08 Apr, 2000 1 commit
-
-
Ken Manheimer authored
parent is killed first. (Otherwise, sometimes - often - a new child was being spawned before the parent was clobbered, and the zeo server survived...)
-
- 06 Apr, 2000 1 commit
-
-
Christopher Petrilli authored
-
- 23 Mar, 2000 1 commit
-
-
Jim Fulton authored
-
- 22 Mar, 2000 3 commits
-
-
Michel Pelletier authored
-
Michel Pelletier authored
-
Jim Fulton authored
-
- 06 Mar, 2000 1 commit
-
-
Jim Fulton authored
called TimeStamp_yad inconsistently. Now both TimeStamp_abst and TimeStamp_yad are called with "0-based" non-adjusted years.
-
- 11 Jan, 2000 1 commit
-
-
Jim Fulton authored
management of pool lock.
-
- 10 Dec, 1999 2 commits
-
-
Jim Fulton authored
were not handled correctly.
-
Jim Fulton authored
fsync when commiting transactions to make sure that transaction data are written to physical storage immediately. There is circumstantial evidence that database corruption has been caused due to problems with delayed write of data after Zope has flushed transaction data. Added logic to avoid writing empty transactions. It's imaginable that some future application might want to write empty transactions to capture transaction meta data. If this ever becomes an issue, then this feature would have to be made optional.
-
- 09 Dec, 1999 2 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
Added utility code to recover corrupted databases. Note that the recover method is imperfect. It doesn't recover lost data. It just repairs the file so the lost data doesn't prevent startup. To run the recovery code: - cd lib/python - python ZODB/fsrecover.py ../../var/Data.fs
-
- 07 Dec, 1999 1 commit
-
-
Jim Fulton authored
- Restart or pack Zope, causing an index to get written - Undo some transactions - Shutdown Zope ungracefully (e.g. kill) When Zope comes up, the index points to undone records for some objects. This can lead to all sorts of problems. :( To overcome this problem, we now remove the index after an undo. This increases the likelyhood that it will take longer to restart next time, but reduces the chance of a bad index.
-
- 23 Nov, 1999 3 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
Renamed some classes to make their intent clearer. Fixed a silly typo in zrpc.
-
- 16 Nov, 1999 8 commits
-
-
Christopher Petrilli authored
-
Christopher Petrilli authored
-
Christopher Petrilli authored
-
Christopher Petrilli authored
-
Christopher Petrilli authored
-
Christopher Petrilli authored
-
Christopher Petrilli authored
-
Christopher Petrilli authored
-