Issue 949627
Created on 2004-05-07 02:50 by eparker, last changed 2017-02-26 16:37 by rouilj.
msg3320 |
Author: [hidden] (eparker) |
Date: 2004-05-07 02:50 |
|
Hello,
I'm trying to set up a new tracker, and I'm realizing
that in order to flush out all our existing issues, and
populate it with an existing tracker's issues and
settings, I'll need to run a SQL query on the backend
to dump all it's juiciness.
I was thinking it would b nice if roundup-admin had
something like roundup-admin intialise, except have it
*not* initialise -- just dump the database.
ie., roundup-admin clean, or roundup-admin nuke or
something.
Thanks!
|
msg5937 |
Author: [hidden] (rouilj) |
Date: 2017-02-26 16:37 |
|
This is very old, but does roundup-admin init do the trick?
It seems like it calls: tracker.nuke() which should remove the old
database.
You may need to rm -rf db/*
to remove the msgs and files subdirs where files contents are stored.
In newer (1.6) releases the database backend is stored in config.ini
and not in db/backends so I think even an rm -rf db will work without
losing anything important.
|
|
Date |
User |
Action |
Args |
2017-02-26 16:37:44 | rouilj | set | status: open -> closed resolution: accepted messages:
+ msg5937 nosy:
+ rouilj |
2004-05-07 02:50:19 | eparker | create | |
|