I would create a table with 2 columns as a key, value pair and set the key to be unique. That way, a setting could not be duplicated. Yet, you could add as many different settings as you want without altering the model at any point in the future. I suppose one could then add invalid/non-existent settings, but if the code doesn't check for them, no harm is done.
On 6/16/06, bradford <[EMAIL PROTECTED]> wrote: > > I need a model called settings that has some application settings the > user can edit in the admin. How should I set this model up so that one > and only one settings record always exists for the lifetime of the > application. > > Also, please let me know if this approach is incorrect. > > > > > -- ---- Waylan Limberg [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
