I'm writing a Django app to act as the front-end interface to a backup application, using MySQL as the database. I need to store some variables to act as the "global" settings specific to my app - like UNIX backup location, etc.
At present I have a model called Setting, with two fields - name and value. The problem with this, however, is that if the project is reset - as it often is at the moment as I am playing around with the models a lot - all the rows in the settings table are lost, and therefore all the values. Is there a commonly "accepted" way to achieve what I am doing here? How does one store variables which don't really conform strictly to the "model". I want these values to be changeable via views in the web interface. Thanks for any input, Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
