I see. Although I would be interested to see what you come up with, my initial reaction is that we wouldn't accept a patch for Django to do this. It seems too complex and brittle.
I agree with Melvyn that it seems unusual to use Django's multi-database facilities to transfer data between staging and production. On Wednesday, November 9, 2016 at 4:51:39 AM UTC-5, Melvyn Sopacua wrote: > > On Wednesday 09 November 2016 13:59:35 Mike Dewhirst wrote: > > On 9/11/2016 9:13 AM, Tim Graham wrote: > > > Interesting idea. I'd be interested to here more about the use case. > > > > Simple. I permitted my users to "play" on the staging site and now one > > of them wants to transfer their work to the production site. > > Your approach is wrong. You think of this as one django project and > trying to cheat under the hood, while in fact they are two different > projects. And by design, staging is not always structually identical to > production. > > Your best approach is to use serialization with natural keys and a job > scheduler. Cron will do, but there's plenty other schemes allowing you > to provide feedback about the job queue and expected time of completion. > -- > Melvyn Sopacua > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/ccfa9aef-d1c3-45e0-a894-c07a2701c1aa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
