Hi, We have a legacy Django application that parses configuration files for several in-house applications, builds up a map of those applications, including any network connections between them (based on IP address and port), then stores them in Django models.
Each application object will store several things, such as a process name (which is unique), the application binary and version, as well as any network connections (listening or connecting). For simplicity (I'm assuming), each day they blow away the existing model instances, then reparse all the configuration, and build up a new map with new model instances. I'm looking at using similar to django-reversion to add version control to this application (It probably will be django-reversion - I'm not aware of any viable alternatives to django-reversion). Now, obviously, the current blowing away approach isn't going to work with Django-reversion. However, say we do a re-parse, what's the best way of integrating django-reversion into the workflow? I assume we'd need some way of linking an existing application model with the new one from each daily re-parse. We could use the process name (which is unique), do a lookup to see if that process name already exists, get it if it does, write our new values to the model, then save it. My understanding is that django-reversion will only pickup on the changed fields. We'd need to do a lookup on every single application and a save though - there's probably a smarter way to bulk these? (I know there's bulk create in Django, I'm not aware of any bulk updates?). Are there any performance considerations we should be wary of? (There are probably between 100-200 applications). Cheers, Victor -- 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 http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
