On 16 juin, 22:23, ocgstyles <[EMAIL PROTECTED]> wrote: > The client wants certain parts of the site to be editable, I don't > particularly agree with the logic, simply because why take a DB hit > (although small) just to grab text from a database for an "About" page > when that text us USUALLY static.
This is easily cured by using a cache, and Django does have a cache system, so I wouldn't worry that much about this point. Anyway, most CMS are just that - db storage for mostly static content !-) Also and FWIW, there's also and already a Django app for this - Flatpage. But anyway, even if you roll your own, I don't get why you should want to restrict to only one instance - what you want (IMVHO) as a model is not an "About", it's a general mechanism for storing text fragments. In this case, I'd go for something with a slug as primary key (or as unique field in addition to an auto primary key), and a convention that the 'about' page (or fragment of..) is slugged "about". My 2 cents... (snip) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
