1515# BASIS, AND THERE IS NO OBLIGATION WHATSOEVER TO PROVIDE MAINTENANCE,
1616# SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
1717#
18- #$Id: back_bsddb.py,v 1.14 2002-01-22 07:21:13 richard Exp $
18+ #$Id: back_bsddb.py,v 1.15 2002-02-16 09:15:33 richard Exp $
1919'''
2020This module defines a backend that saves the hyperdatabase in BSDDB.
2121'''
@@ -88,9 +88,9 @@ def getjournal(self, classname, nodeid):
8888 journal = marshal .loads (db [nodeid ])
8989 res = []
9090 for entry in journal :
91- (nodeid , date_stamp , self . journaltag , action , params ) = entry
91+ (nodeid , date_stamp , user , action , params ) = entry
9292 date_obj = date .Date (date_stamp )
93- res .append ((nodeid , date_obj , self . journaltag , action , params ))
93+ res .append ((nodeid , date_obj , user , action , params ))
9494 db .close ()
9595 return res
9696
@@ -109,6 +109,14 @@ def _doSaveJournal(self, classname, nodeid, action, params):
109109
110110#
111111#$Log: not supported by cvs2svn $
112+ #Revision 1.14 2002/01/22 07:21:13 richard
113+ #. fixed back_bsddb so it passed the journal tests
114+ #
115+ #... it didn't seem happy using the back_anydbm _open method, which is odd.
116+ #Yet another occurrance of whichdb not being able to recognise older bsddb
117+ #databases. Yadda yadda. Made the HYPERDBDEBUG stuff more sane in the
118+ #process.
119+ #
112120#Revision 1.13 2001/12/10 22:20:01 richard
113121#Enabled transaction support in the bsddb backend. It uses the anydbm code
114122#where possible, only replacing methods where the db is opened (it uses the
0 commit comments