manage.py dumpdata
On Sun, Jun 30, 2013 at 10:40 AM, Mike Dewhirst <[email protected]>wrote: > This is probably a Postgres question but someone might be able to offer > advice on how to transfer data :) > > New "reference" or read-only data gets input during development and I want > to transfer it to the production database from time to time. > > I think my choices are: > > 1. Re-enter it manually - only if all else fails. > > 2. Use Django's multi-database feature and write a utility to transfer > data which doesn't already exist. Except the databases are on different > machines in different data centres. > > 3. Exploit some pre-existing tool written for precisely this problem. > > Any suggestions? > > There are currently three reference tables involved and two have m2m > relationships between themselves. The other is stand-alone. > > Customer data is fine in the production database and won't be touched. > There are no relationships with the reference tables. > > Thanks > > Mike > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > django-users+unsubscribe@**googlegroups.com<django-users%[email protected]> > . > To post to this group, send email to [email protected]. > Visit this group at > http://groups.google.com/**group/django-users<http://groups.google.com/group/django-users> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
