On 12/4/06, Phil Powell <[EMAIL PROTECTED]> wrote: > I have a "Homepage" which has fields such as "Page Title", > "Introduction Text", "Footer Text" etc. I want to be able to edit > these fields just like I'd edit a standard model instance, but because > there is only one instance of my "Homepage" I never want more than one > instance of it to exist.
So don't ever create more than one instance of it ;) Regardless of feelings about the Singleton pattern (I'm not a fan), though, this isn't really something that will have a clean solution in Django, if it has a solution at all; because Django model classes map to tables in a relational database, they carry with them the inherent idea of being able to create multiple instances (which would then correspond to multiple rows. You *might* be able to hack something together using one of the various attempts people have made at implementing Singleton in Python [1], but I personally wouldn't recommend it. [1] http://aspn.activestate.com/ASPN/search?query=singleton&x=0&y=0§ion=PYTHONCKBK&type=Subsection -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
