Interesting idea. I'd be interested to here more about the use case. How would it work for entities with a foreign key? Django assumes foreign keys can't be cross-database since the constraint can't be enforced.
On Tuesday, November 8, 2016 at 4:29:48 PM UTC-5, Mike Dewhirst wrote: > > I'd like to use the [Save as new] infrastructure to transfer records and > their children to a different database. > > Can anyone give me some advice on whether this is a reasonable project > to attempt? Would it be valuable for anyone else? > > My alternative is to build a separate mechanism for my own use. Which I > have started but I can see it is going to get overly complex. > > 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+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/7d1bd5c7-cffa-4b4a-bf1b-7dbb1e18f504%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
