As far as I know, there's no way to restrict the number of instances of a particular model. You could hack the admin templates to hide "Add" buttons if an instance of a particular model already exists. Or override the save method in the model so that it doesn't save if an instance already exists (which would be a bit confusing for an admin user, and probably a bad idea)
-Phil On 16/06/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. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
