Geek Answers Handbook

Django The original data process is loading.

I worked on improving and refactoring some 57k + records from two legacy databases into one Jango-compatible object. Now that I have finished, I reset it as a tool and I am trying to load it in a production environment.

My problem is that after a while the process is "killed". My process:

./manage.py syncdb --noinput
./manage.py loaddata core/fixtures/auth.json  # just a default user
./manage.py migrate

result:

Running migrations for django_extensions:  # custom apps migrate just fine
 - Migrating forwards to 0001_empty.
 > django_extensions:0001_empty
 - Loading initial data for django_extensions.
Installed 0 object(s) from 0 fixture(s)
Running migrations for myotherapp:
 - Migrating forwards to 0001_initial.
 > myotherapp:0001_initial
 - Loading initial data for myotherapp.
Installed 4 object(s) from 1 fixture(s)  # my other app with a fixture migrates ok
Running migrations for myapp:
 - Migrating forwards to 0001_initial.
 > myapp:0001_initial
 - Loading initial data for myapp.
Killed

I should note that the process goes smoothly on my development machine. One more note: my dev machine works with postgres 9.2, in production 9.1 - maybe this is a big problem?

How do I go about debugging? I don’t even know what’s wrong, because of the vague "killed." Are there magazines in the South store? Any help was appreciated.

EDIT: , , JSON . XML-, , . - SQL-. Postgres , , :

pg_dump dbname | gzip > filename.gz # dump data on dev machine
createdb dbname # create empty db in production
gunzip -c filename.gz | psql dbname # restore the dump in production
+4
1

. , , :

:

, XML- , XML .

- , SQL-, .

+5

More articles:


All Articles