Description

This tool is used for dump and restore database of Django. And it can also support some simple situations for Model changes, so it can also be used in importing data after the migration of Model.

It includes: dump and restore.

Dump

Command Line:

python db_dump.py [-svdh] [--settings] dump [applist]

If applist is ignored，then it means that all app will be dumped. applist can be one or more app name.

Description of options:

• -s Output will displayed in console, default is writing into file
• -v Display execution infomation, default is does not display
• -d Directory of output, default is datadir in current directory. If the path is not existed, it'll be created automatically.
• -h Display help information.
• --settings settings model, default is settings.py in current directory.

It can only support Python format for now. It'll create a standard python source file, for example:

dump = {'table': 'tablename', 'records': [[...]], 'fields': [...]}

table' is table name in database, records is all records of the table, it's a list of list, that is each record is a list. fields` is the fields name of the table.

Load(Restore)

Command Line:

python db_dump.py [-svdrh] [--settings] load [applist]

You can refer to the above description for same option. Others is:

• -r Does not empty the table as loading the data, default is empty the table first then load the data

Using this tool, you can not only restore the database, but also can deal with the simple changes of database. It can select the suitable field from the backup data file according to the changed Model automatically, and it can also deal with the default value define in Model, such as default parameter and auto_now and auto_now_add parameter for Date-like field. And you can even edit the backup data file manually, and add a default key for specify the default value for some fields, the basic format is:

'default':{'fieldname':('type', 'value')}

default is a dict, the key will be the field name of the table, the value will be a two element tuple, and the first element of this tuple is type field, the second element is its value. Below is a description of type field:

| Type | Value | Description | |:---------|:----------|:----------------| | 'value' | real value | using the value field directly | | 'reference' | referred field name | the value of this filed will use the value of referred field. It'll be used when the field name is changed | | 'date' | 'now'|'yyyy-mm-dd' | It's a date date type, if the value field is 'now', then the value be current time. Otherwise, it'll be a string, it's format is 'yyyy-mm-dd' | | 'datetime' | 'now'|'yyyy-mm-dd hh:mm:ss' | The same as above | | 'time' | 'now'|'hh:mm:ss' | The same as above |

The strategy of selection of default value of a field is: first, create a default value dict according the Model, then update it according the default key of backup data file. So you can see if there is a same definition of a field in both Model and backup data file, it'll use the one in backup data file.

According the process of default value, this tool will suport these changes, such as: change of field name, add or remove field name, etc. So you can use this tool to finish some simple update work of database.

But I don't give it too much test, and my situation is in sqlite3. So download and test are welcome, and I hope you can give me some improve advices.

How to use it

1. download it and extract to your Django project directory and put it with settings.py together
2. run it in the command line according to the above description

Change Log

1. Version 2.1 2007-09-18
   • add Time type support
2. Version 2.0 2007-09-11
   • refact, and add aoto reset postgres sequence
3. Version 1.9 2007-09-02 (Merge from RichardH)
   • Adds try-except to catch the changes in db.backend refactoring in svn version. So db_dump.py can support old version except trunk.
4. Version 1.8 2007-08-30
   • Fix backend.quote_name to backend.DatabaseOperations().quote_name Thanks to richardh
5. Version 1.7 2007-05-28
   • keep up with the change of GenericRel, so you can use db_dump.py in trunk and version before 0.97
6. Version 1.6 2007-04-09
   • Add float support
7. Version 1.5 2007-02-08
   • If the filename is not exists, then skip it
8. Version 1.4 2007-01-21
   • support mysql
9. Version 1.3 2007-01-20
   • change the output format of data file, and improve the process effective of dumpping and loading
10. Version 1.2 2007-01-20
    • change dumpdb to use model info but not cursor.description, because some database backend does not support cursor.description
11. Version 1.1 2007-01-19
    • if no arguments after db_dump.py, then it'll show help infomation
12. Version 1.0 2007-01-18