Roundup Tracker - Issues

Issue 570224

classification
db.commit() doesn't
Type: Severity: normal
Components: Database Versions:
process
Status: closed invalid
:
: richard : gmcm, richard
Priority: normal :

Created on 2002-06-17 21:30 by gmcm, last changed 2002-06-18 15:51 by gmcm.

Messages
msg274 Author: [hidden] (gmcm) Date: 2002-06-17 21:30
Using anydbm (which is using dumbdbm) on RH 7.0 box
(kept up to date with redcarpet) and Python 2.1.1.

Wrote a script to convert a bugs from one BTS to Roundup.
The script opens the db once, loops through all the
bugs, with a db.commit() after each bug. After 2,000 or
so bugs, I ran out of disk space. None of the bugs (or
users, or keywords) added show up.

msg275 Author: [hidden] (richard) Date: 2002-06-17 23:11
Logged In: YES 
user_id=6405

Hrm. Which db is anydbm using? Looks like there's a commit   
missing in the backend somewhere. It does a close() of all the  
backend dbs on a hyperdb commit, but maybe something else  
is missing...  
  
Note that the HYPERDBDEBUG env var can be used to dump  
the hyperdb's activities.  
  
msg276 Author: [hidden] (gmcm) Date: 2002-06-18 15:51
Logged In: YES 
user_id=4923

It's using gdbm.

There's a problem here, but I screwed up and it's not as
described.
The 1st commit worked, the second fails with "resource
temporarily unavailable" on nodes.keyword. In fact,
nodes.keyword seems now to be permanently unavailable
(except for reading).

I'll close this and open a new one when I figure out what's
really going on.
History
Date User Action Args
2002-06-17 21:30:12gmcmcreate