Hi, no problem.
> Thanks a lot. Yes this is definitely an option if source and target host > the same database engine. > > > The reason why would I like to avoid this approach and why I tried to > stick with django commands is, that above approach will not work if I > want to dump a postgres database to a test machine which has only sqlite > or mysql. > > Therfore my motivation was to use dumpdata and loaddata of manage.py I was doing the same before, too: Having different DBs on dev machine and server. Because it was so much trouble maintaining the two using dumpdata and loaddata I ended up using the same DB on both machines which is also a good idea if you don’t want to run into any other surprises which are provoked by different DBs. > Concerning above approach for mysql: > > I think it is not necessary to provide the password in the command > line. If I remember well one can create a temp file with permissions 600 > and store the user/password in it > and specify it on the command line with > --defaults-file=tmp_my.cnf absolutely right. I even have that file and forgot to use it when I looked up the command in web. > However as I don't use postgres that much I don't know whether postgres > can do the same (specify a non default config file) I bed it does. Just look around a little. BTW: This testmachine should even have the same webserver as the real server so your testing is actually a little more accurate. Bye and good luck -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
