I have a task which looks simple at the first sight: Setting up a system for testing by users.
In my case it is a custom issue tracking system. The users who should do the testing say "The new system should be like the production system." If this would be true, then dump+restore of the database should work. No Nr2: the production system contains a lot of issues, and these should not be in the new system. No Nr2: The production system contains configuration (in the database) of remote storage systems. These database rows must not get copied, otherwise the testing system would transfer testing data to the production storage system. Configuration like the list of ticket types should get copied. Tables are tables, or is there a difference between tables? Up to now I only found one hint to this task: In SAP this is called "client copy" and there seem to be different "delivery classes" of a table: https://help.sap.com/doc/saphelp_crm70/7.0.0.18/en-US/43/45860774b711d2959700a0c929b3c3/content.htm?no_cache=true Are there tools/framework which support copying a system? I am curious, if you know a framework outside django, please tell me. Up to now I could not find a tool or hint about solving this in a reusable way in django. If I was blind, please let me know. Any kind of feedback is welcome. Regards, Thomas Gütler -- 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/4b410060-3acc-4ddc-87c3-aa9c2af750c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
