mirror of
https://github.com/peeringdb/peeringdb.git
synced 2024-05-11 05:55:09 +00:00
30 lines
638 B
Markdown
30 lines
638 B
Markdown
|
## undelete
|
||
|
|
|
||
|
|
First find out the version id when the object was deleted
|
||
|
|
|
||
|
|
```
|
||
|
|
python manage.py pdb_reversion_inspect <reftag> <id>
|
||
|
|
```
|
||
|
|
|
||
|
|
```
|
||
|
|
VERSION: 7 (392112) - 2018-12-24T07:13:49.612Z - User: XXX
|
||
|
|
status: 'ok' => 'deleted'
|
||
|
|
```
|
||
|
|
|
||
|
|
You want the number inside the brackets (in this case *392112*)
|
||
|
|
|
||
|
|
Then run the undelete command
|
||
|
|
|
||
|
|
```
|
||
|
|
python manage.py pdb_undelete <reftag> <id> <version id>
|
||
|
|
```
|
||
|
|
|
||
|
|
This will show you everthing that will be undeleted, it will run in pretend mode, nothing
|
||
|
|
is committed yet.
|
||
|
|
|
||
|
|
After reviewing, run the command again with the `--commit` flag
|
||
|
|
|
||
|
|
```
|
||
|
|
python manage.py pdb_undelete <reftag> <id> <version id> --commit
|
||
|
|
```
|