django, postgresql: moving dumped database data from one machine to another

Question

I am trying to move dumped data from postgresql database to another. However, when syncdb is run on django, it inserts some values into the database. When I then want to insert the dump into the database, I get conflicts. What is the right way of moving some data from one django built database to another?

Do you have any reason not to dump the schema and the data and use that without running syncdb? — Sam Dolan
– Sam Dolan, Commented Jun 14, 2010 at 17:46

Szymon Lipiński · Accepted Answer · 2010-06-14 18:33:58Z

1

Get rid of syncdb, instead perform a normal database dump and restore it on the other database

answered Jun 14, 2010 at 18:33

Szymon Lipiński

28.8k17 gold badges81 silver badges82 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

gruszczy Over a year ago

I am also migrating from 1.1 to 1.2. Won't I break anything?

Szymon Lipiński Over a year ago

I don't know - just check it. You can always perform syncdb on the new database and compare the databases. First of all compare the structure, simple pg_dump from both databases and diff should work. Then you just could the same way perform dump of each table from one database and another and compare them. This way you should be able to do just the syncdb on the new database and load the prepared sql script to load missing data. Or maybe just look carefully at the errors that you've got, maybe it would be enough just to fix them.

gruszczy Over a year ago

Thanks, sounds reasonable :-)

Collectives™ on Stack Overflow

django, postgresql: moving dumped database data from one machine to another

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related