- 10 Jul, 2004 1 commit
-
-
Tim Peters authored
Repaired a bug wherein spurious error msgs could be produced after reporting a problem with an unloadable object (discovered by eyeball, while staring at the code to figure out what it actually does). Vastly expanded the module docstring, with a slimmed-down version of the new fsrefs docs on the ZODB Wiki.
-
- 08 Jul, 2004 2 commits
-
-
Tim Peters authored
Zope3-dev Collector #139: Memory leak involving buckets and connections Connection objects were typically immortal because the threaded transaction manager kept them in ever-growing lists. Reworked the transaction manager internals to use a simple implementation of weak sets instead. This plugs all leaks in the test program attached to the collector report (which was leaking about 100KB/sec on my box).
-
Tim Peters authored
Connection objects were typically immortal because the threaded transaction manager kept them in an ever-growing lists. Reworked the transaction manager internals to use a simple implementation of weak sets instead. This plugs all leaks in the test program attached to the collector report (which was leaking about 100KB/sec on my box).
-
- 02 Jul, 2004 2 commits
-
-
Tim Peters authored
Forward-porting from Zope 2.7. Merged from 3.3 branch, revision 26085. The checkFullTimeStamp() test was sensitive to unique mktime() behavior on FreeBSD. See: http://lists.freebsd.org/pipermail/freebsd-standards/2003-November/000268.html The purpose of this test is to exercise ZODB's TimeStamp object, so got rid of dependence on platform mktime() and time.timezone quirks -- TimeStamp works in GMT, so how mktime() treats tm_isdst should be irrelevant in all TimeStamp tests. Also added a comment about the highly non-obvious numeric characteristics of TimeStamp's treatment of seconds (round-tripping is surprisingly inaccurate, but for a real reason).
-
Tim Peters authored
Forward-porting from Zope 2.7. The checkFullTimeStamp() test was sensitive to unique mktime() behavior on FreeBSD. See: http://lists.freebsd.org/pipermail/freebsd-standards/2003-November/000268.html The purpose of this test is to exercise ZODB's TimeStamp object, so got rid of dependence on platform mktime() and time.timezone quirks -- TimeStamp works in GMT, so how mktime() treats tm_isdst should be irrelevant in all TimeStamp tests. Also added a comment about the highly non-obvious numeric characteristics of TimeStamp's treatment of seconds (round-tripping is surprisingly inaccurate, but for a real reason).
-
- 29 Jun, 2004 4 commits
-
-
Tim Peters authored
intend real implementations to work, and beefed up the tests to match. The collaboration also got a little simpler.
-
Tim Peters authored
-
Tim Peters authored
New interface IResourceManager intends to combine the best aspects of IDataManager and IDataManagerOriginal, and will become "the" interface. New interface ISavePoint captures (along with models in collaborations.txt) what should be a clean design for a savepoint/rollback facility that actually works.
-
Jim Fulton authored
Updated an old collaboration to reflect the change.
-
- 28 Jun, 2004 1 commit
-
-
Tim Peters authored
are in now (partly ZODB 3, partly ZODB 4, partly transitional). More is needed. Added new collaborations.txt, which spells out some dynamics of the system in a compact way. This is in a format Jim used for Zope 3, essentially a flat-text and less-formal representation of UML sequence diagrams.
-
- 25 Jun, 2004 1 commit
-
-
Tim Peters authored
No commit message
-
- 22 Jun, 2004 5 commits
-
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
and include that in the ZODB project. While we're at it, include zope.testing too, as zope.interface depends on that, and we had copied zope.testing.loggingsupport.py into ZODB earlier anyway (and delete that unique copy here now). This also merges some changes made to the ZODB copy in Zope3 back into ZODB.
-
- 21 Jun, 2004 4 commits
-
-
Tim Peters authored
Collector 1327: FileStorage init confused by time travel If the system clock moved back in time more than 30 days between a FileStorage close and (re)open, new txn ids could be smaller than txn ids already in the database. Plugged that hole.
-
Tim Peters authored
If the system clock moved back in time more than 30 days between a FileStorage close and (re)open, new txn ids could be smaller than txn ids already in the database. Plugged that hole.
-
Tim Peters authored
-
Tim Peters authored
-
- 18 Jun, 2004 2 commits
-
-
Tim Peters authored
New test checkRestoreWithMultipleObjectsInUndoRedo from ZODB 3.2.2. 3.3 didn't have the bug, and this confirms it.
-
Tim Peters authored
3.3 didn't have the bug, and this confirms it.
-
- 17 Jun, 2004 2 commits
-
-
Tim Peters authored
-
Tim Peters authored
-
- 15 Jun, 2004 3 commits
-
-
Fred Drake authored
(identical to revision 25416 on the ZODB-3.3 branch, but svn would not merge the change)
-
Fred Drake authored
-
Fred Drake authored
-
- 08 Jun, 2004 12 commits
-
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Fred Drake authored
(equivalent to revision 25293 on the ZODB 3.3 branch, but not a merge, since the files were added separately after the branch was made)
-
Fred Drake authored
-
- 07 Jun, 2004 1 commit
-
-
Fred Drake authored
move the release metadata for zpkg here from the CVS repository; this was in Releases/ZODB3/ on cvs.zope.org
-